Triple
T26276080
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Durg–Bhilai–Raipur urban corridor |
E660572
|
entity |
| Predicate | stateCapitalLocatedAt |
P114431
|
FINISHED |
| Object | Raipur |
—
|
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: Raipur | Statement: [Durg–Bhilai–Raipur urban corridor, stateCapitalLocatedAt, Raipur]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stateCapitalLocatedAt Context triple: [Durg–Bhilai–Raipur urban corridor, stateCapitalLocatedAt, Raipur]
-
A.
stateCapitalLocatedHere
chosen
Indicates that the capital city of a state is geographically located at or within the referenced place.
-
B.
governingStateCapital
Indicates that a state serves as the governing political authority over the specified capital city.
-
C.
capitalOfMajorState
Indicates that one location serves as the primary capital city of a major state or significant administrative region.
-
D.
capitalOfStateLocatedOn
Indicates that one entity is the capital city of a state in which the other entity is geographically located.
-
E.
stateCapitalForRegionLocatedAt
Indicates that a city serves as the capital of a particular region and is geographically located at that region.
- 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_69ee812960d081909cff6085cc9fa3a6 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f6c49627908190b3553474c7c3072b |
completed | May 3, 2026, 3:44 a.m. |
| PD | Predicate disambiguation | batch_69f6c3f23ae081909a52801266063a3c |
completed | May 3, 2026, 3:41 a.m. |
Created at: April 26, 2026, 9:55 p.m.