Triple
T18453701
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rajasuya sacrifice of Yudhishthira |
E450848
|
entity |
| Predicate | timeInEpic |
P20414
|
FINISHED |
| Object | after building of Indraprastha |
—
|
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: after building of Indraprastha | Statement: [Rajasuya sacrifice of Yudhishthira, timeInEpic, after building of Indraprastha]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeInEpic Context triple: [Rajasuya sacrifice of Yudhishthira, timeInEpic, after building of Indraprastha]
-
A.
timeInMyth
chosen
Indicates that an entity exists or occurs during a specific time period within a mythological narrative or tradition.
-
B.
timePeriod
Indicates the specific span or interval of time during which an event, state, or relationship occurs or is valid.
-
C.
timeCoMainEvent
Indicates that two or more events occur as co-main events at the same time or within the same overarching event timeframe.
-
D.
timeExistence
Indicates the period or duration during which an entity exists or is valid.
-
E.
eraDuration
Indicates the length of time that a particular era or period spans.
- 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_69d8d38345688190b565eac2e4cd7935 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e5264a49ec8190aa43381d93a55e91 |
completed | April 19, 2026, 7 p.m. |
| PD | Predicate disambiguation | batch_69e469d05cf4819099baf1665a9cf18a |
completed | April 19, 2026, 5:36 a.m. |
Created at: April 10, 2026, 11:31 a.m.