Triple
T5129637
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Indraprastha |
E115663
|
entity |
| Predicate | postWarFateInTradition |
P12962
|
FINISHED |
| Object | reintegrated into the Kuru realm under the Pandavas |
—
|
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: reintegrated into the Kuru realm under the Pandavas | Statement: [Indraprastha, postWarFateInTradition, reintegrated into the Kuru realm under the Pandavas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: postWarFateInTradition Context triple: [Indraprastha, postWarFateInTradition, reintegrated into the Kuru realm under the Pandavas]
-
A.
postwarOutcome
chosen
Indicates the result or consequences that follow for a party or situation after a war has ended.
-
B.
usedAfterWar
Indicates that an entity came into use only after a specific war or conflict had ended.
-
C.
postWarOccupation
Indicates that one entity occupied, administered, or controlled another entity or territory in the period following a war.
-
D.
statusAfter1942
Indicates the status or condition of an entity as it existed after the year 1942.
-
E.
warEndedHere
Indicates that a particular war or armed conflict came to its conclusion at this location.
- 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_69bd444426bc819099ccd23f141e22aa |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd7fef2e8c8190982dd67f50295ada |
completed | March 20, 2026, 5:12 p.m. |
| PD | Predicate disambiguation | batch_69bd77ac2fc48190abeebb003a82384c |
completed | March 20, 2026, 4:37 p.m. |
Created at: March 20, 2026, 1:42 p.m.