Triple
T32003400
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mumbai–Hyderabad line |
E817192
|
entity |
| Predicate | majorJunctionState |
P197929
|
FINISHED |
| Object | Maharashtra |
—
|
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: Maharashtra | Statement: [Mumbai–Hyderabad line, majorJunctionState, Maharashtra]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: majorJunctionState Context triple: [Mumbai–Hyderabad line, majorJunctionState, Maharashtra]
-
A.
isMajorJunctionCode
Indicates that a given code corresponds to a major junction point within a network (such as transport, communication, or infrastructure).
-
B.
significantJunction
Indicates a junction or intersection that plays an important or central role in connecting routes or pathways.
-
C.
hasJunctionStatus
Indicates the status or condition of a junction within a system or network.
-
D.
majorState
Indicates that a state holds significant power, influence, or importance relative to other states within a given system or context.
-
E.
isMajorRoadJunction
Indicates that a location serves as a primary intersection where major roads or highways meet or cross.
- 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_69f348f8ce388190ae84376b1f348f12 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69feba0f09508190b3e871c62b19ec7f |
completed | May 9, 2026, 4:37 a.m. |
| PD | Predicate disambiguation | batch_69feb957fe7c8190969fb31a6d1a59c8 |
completed | May 9, 2026, 4:34 a.m. |
| PDg | Predicate description generation | batch_69feba0e362c81909883a3f24a4a9545 |
completed | May 9, 2026, 4:37 a.m. |
Created at: May 1, 2026, 12:14 a.m.