Triple
T30649195
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ikshvaku |
E780207
|
entity |
| Predicate | regionInMythology |
P189930
|
FINISHED |
| Object | ancient northern India |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: ancient northern India | Statement: [Ikshvaku, regionInMythology, ancient northern India]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regionInMythology Context triple: [Ikshvaku, regionInMythology, ancient northern India]
-
A.
mythologicalLocation
Indicates that the subject is a place or setting that exists within mythology, legends, or folklore rather than in historical or physical reality.
-
B.
hasMythologicalRegion
chosen
Indicates a relationship where something is associated with, set in, or belonging to a specific mythological or legendary region.
-
C.
linkedToMythology
Indicates that something has a connection or association with a mythological tradition, figure, story, or theme.
-
D.
mythologicalCategory
Indicates that one entity is classified as belonging to the mythological type, group, or category represented by the other entity.
-
E.
centralMythology
Indicates that one entity serves as a core or defining mythological element within the context or tradition of another entity.
- F. None of above.
Provenance (3 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69f224a5d2b481908a6853cd0138e2d7 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fe5c1a502081909d4024e514309c8e |
completed | May 8, 2026, 9:56 p.m. |
| PD | Predicate disambiguation | batch_69fe5a9df21c819087153f5d0bcaa987 |
completed | May 8, 2026, 9:50 p.m. |
Created at: April 29, 2026, 8:30 p.m.