Triple
T25699390
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dispur |
E644413
|
entity |
| Predicate | replacedCapitalOfAssam |
P43447
|
FINISHED |
| Object | Shillong |
—
|
NE NERFINISHED |
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: Shillong | Statement: [Dispur, replacedCapitalOfAssam, Shillong]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: replacedCapitalOfAssam Context triple: [Dispur, replacedCapitalOfAssam, Shillong]
-
A.
replacedByAsCapitalOfBritishIndia
Indicates that one entity ceased to be the capital of British India and was succeeded in that role by another entity.
-
B.
replacedByInJammuAndKashmir
Indicates that one entity has been superseded or substituted by another specifically within the context of Jammu and Kashmir.
-
C.
replacesCapitalCity
chosen
Indicates that one capital city is substituted for or takes over the role of another as the official capital.
-
D.
mandalHeadquartersOf
Indicates that a location serves as the administrative headquarters for a specified mandal (sub-district).
-
E.
isPlannedToBeReplacedAsCapitalBy
Indicates that one capital city is intended or scheduled to be superseded by another as the official capital.
- 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_69e77e82c9bc8190893090b2f6c64f1d |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f638d11c988190af7fd4572b08e038 |
completed | May 2, 2026, 5:48 p.m. |
| PD | Predicate disambiguation | batch_69f63706b6008190993577193c85ff50 |
completed | May 2, 2026, 5:40 p.m. |
Created at: April 21, 2026, 8:42 p.m.