Triple
T25670908
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Akola–Khandwa metre-gauge line |
E643669
|
entity |
| Predicate | startPointState |
P173335
|
FINISHED |
| Object | Maharashtra |
E19223
|
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: Maharashtra | Statement: [Akola–Khandwa metre-gauge line, startPointState, Maharashtra]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: startPointState Context triple: [Akola–Khandwa metre-gauge line, startPointState, Maharashtra]
-
A.
startPoint
Indicates the initial location or position from which an object, path, or action begins.
-
B.
startPointLocatedIn
Indicates that the starting point of something is geographically or spatially located within a specified area or region.
-
C.
startPointDescription
Indicates the textual description that specifies the initial point or location where something begins.
-
D.
endPointState
Indicates the resulting condition or status that an entity or process is in at its termination or final point.
-
E.
trainingStartState
Indicates the initial condition or status of an entity at the moment a training process begins.
- 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_69e77e7f69808190ad27df1006f6037a |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f6b56ed31481908c3e5d749e46bad9 |
completed | May 3, 2026, 2:39 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a10d9f5a2a48190badc5e72f0ef5739 |
completed | May 22, 2026, 10:34 p.m. |
| PD | Predicate disambiguation | batch_69f6b3a5fd8481909433e923c5e24e55 |
completed | May 3, 2026, 2:32 a.m. |
| PDg | Predicate description generation | batch_69f6b49339048190b617a6749f648825 |
completed | May 3, 2026, 2:36 a.m. |
Created at: April 21, 2026, 7:27 p.m.