Triple
T25682924
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chennai–Tiruchirappalli line |
E643988
|
entity |
| Predicate | connectsCapitalOfState |
P173668
|
FINISHED |
| Object | Chennai |
E12324
|
NE 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: Chennai | Statement: [Chennai–Tiruchirappalli line, connectsCapitalOfState, Chennai]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: connectsCapitalOfState Context triple: [Chennai–Tiruchirappalli line, connectsCapitalOfState, Chennai]
-
A.
stateCapitalConnection
Indicates a relationship where one entity is the capital city of a given state or is otherwise connected to that state in its role as capital.
-
B.
connectsCapitalsOf
Indicates a relationship where something serves as a link or route between the capital cities of two regions or countries.
-
C.
governingStateCapital
Indicates that a state serves as the governing political authority over the specified capital city.
-
D.
connectsCapitalOf
Indicates a relationship where one entity serves as the capital city of another entity, linking the capital to the political or administrative unit it represents.
-
E.
regionCapital
Indicates that one entity is the capital city or administrative center of a specified region.
- F. None of above. chosen
Provenance (5 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_69e77e8046888190b07ffa58c7e2c37a |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f6b9a84ff88190ab5a71f7ef1e0dac |
completed | May 3, 2026, 2:57 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a111ae6201881909683cf3986272983 |
completed | May 23, 2026, 3:11 a.m. |
| PD | Predicate disambiguation | batch_69f6b626120c819097c9ad04487570d7 |
completed | May 3, 2026, 2:42 a.m. |
| PDg | Predicate description generation | batch_69f6b8fe147881908ba17483c7b13f05 |
completed | May 3, 2026, 2:54 a.m. |
Created at: April 21, 2026, 8:03 p.m.