Triple
T35447845
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sahibabad |
E1024534
|
entity |
| Predicate | nearestMajorBusTerminal |
P99506
|
FINISHED |
| Object | Anand Vihar ISBT |
—
|
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: Anand Vihar ISBT | Statement: [Sahibabad, nearestMajorBusTerminal, Anand Vihar ISBT]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nearestMajorBusTerminal Context triple: [Sahibabad, nearestMajorBusTerminal, Anand Vihar ISBT]
-
A.
nearestMajorTransportHub
chosen
Indicates that one location is the closest significant transportation center (such as a major train station, airport, or bus terminal) to another location.
-
B.
nearbyTerminus
Indicates that one terminus (end point or final stop) is located close to another terminus in space.
-
C.
nearestRailwayTerminus
Indicates that one location is the closest railway terminus to another specified place.
-
D.
nearestMajorRailwayJunction
Indicates the closest significant railway junction in terms of distance from a given location or entity.
-
E.
hasPublicTransportStop
Indicates that a location or area contains or is served by a public transport stop, such as a bus, tram, or train stop.
- 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_69f76df8089481909f0018266ee881b7 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7a225a77c81908f8953ccfeb14336 |
completed | May 3, 2026, 7:29 p.m. |
| PD | Predicate disambiguation | batch_69f7a06d4f108190bae3ab9ae431d2c7 |
completed | May 3, 2026, 7:22 p.m. |
Created at: May 3, 2026, 4:04 p.m.