Triple
T6215930
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gwalior Junction railway station |
E138986
|
entity |
| Predicate | isMajorJunction |
P64350
|
FINISHED |
| Object | yes |
—
|
LITERAL 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: yes | Statement: [Gwalior Junction railway station, isMajorJunction, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isMajorJunction Context triple: [Gwalior Junction railway station, isMajorJunction, yes]
-
A.
isMajorRoadJunction
Indicates that a location serves as a primary intersection where major roads or highways meet or cross.
-
B.
isMajorJunctionOnLine
chosen
Indicates that a location serves as a primary connecting junction along a particular line or route.
-
C.
isMajorInterchangeFor
Indicates that one location functions as a primary hub where multiple routes or lines connect or transfer between each other for another location.
-
D.
isNumberedJunctionOf
Indicates that a junction (such as a road or rail intersection) has been assigned an official identifying number within a network.
-
E.
isMajorArterialFor
Indicates that something functions as a primary high-capacity route or conduit serving as a main channel for movement, flow, or traffic for something else.
- 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_69c008aecb0c81909984b48f733ce8ae |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c062a1eb3881908c7f735cf9c429ce |
completed | March 22, 2026, 9:44 p.m. |
| PD | Predicate disambiguation | batch_69c055fdea3c81908f5d910f0d36234a |
completed | March 22, 2026, 8:50 p.m. |
Created at: March 22, 2026, 4:21 p.m.