Triple
T30132287
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nagpur–Wardha section |
E765876
|
entity |
| Predicate | connectsMajorJunctions |
P64350
|
FINISHED |
| Object | Nagpur Junction |
—
|
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: Nagpur Junction | Statement: [Nagpur–Wardha section, connectsMajorJunctions, Nagpur Junction]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: connectsMajorJunctions Context triple: [Nagpur–Wardha section, connectsMajorJunctions, Nagpur Junction]
-
A.
connectsMajorHub
Indicates that one entity serves as a link or route between major hubs or primary nodes in a network.
-
B.
isMajorJunctionCode
Indicates that a given code corresponds to a major junction point within a network (such as transport, communication, or infrastructure).
-
C.
isMajorRoadJunction
Indicates that a location serves as a primary intersection where major roads or highways meet or cross.
-
D.
isMajorInterchangeFor
Indicates that one location functions as a primary hub where multiple routes or lines connect or transfer between each other for another location.
-
E.
isMajorJunctionOnLine
chosen
Indicates that a location serves as a primary connecting junction along a particular line or route.
- 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_69f22477d1a081908df2b7e6ed16859d |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fdec5ffe088190ac5505f26c6cff18 |
completed | May 8, 2026, 2 p.m. |
| PD | Predicate disambiguation | batch_69fdeae15f1c81908fc63fbc1b028d2e |
completed | May 8, 2026, 1:53 p.m. |
Created at: April 29, 2026, 7:15 p.m.