Triple
T25670910
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Akola–Khandwa metre-gauge line |
E643669
|
entity |
| Predicate | endPointState |
P158970
|
FINISHED |
| Object | Madhya Pradesh |
—
|
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: Madhya Pradesh | Statement: [Akola–Khandwa metre-gauge line, endPointState, Madhya Pradesh]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: endPointState Context triple: [Akola–Khandwa metre-gauge line, endPointState, Madhya Pradesh]
-
A.
endPoint
Indicates the terminal location, limit, or final state reached by an object, process, or path in a given relationship or action.
-
B.
endPointExample
Indicates that something serves as a representative or illustrative instance of a particular endpoint.
-
C.
endOfState
Indicates the point or condition at which a particular state, situation, or process comes to an end.
-
D.
hasEndpointStation
Indicates that something (such as a route, line, or service) has a specific station as one of its terminal endpoints.
-
E.
epicenterState
Indicates the state in which the epicenter of an event (typically an earthquake) is located.
- F. None of above. chosen
Provenance (4 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_69e77e7f69808190ad27df1006f6037a |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f5fb32c33481908a4a182c708b96fe |
completed | May 2, 2026, 1:25 p.m. |
| PD | Predicate disambiguation | batch_69f4807f8680819098a524158d049c63 |
completed | May 1, 2026, 10:29 a.m. |
| PDg | Predicate description generation | batch_69f48b9058d081908ec9af261ee092e2 |
completed | May 1, 2026, 11:16 a.m. |
Created at: April 21, 2026, 7:27 p.m.