Triple
T35447672
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shaheed Sthal |
E1024530
|
entity |
| Predicate | isMajorBusTerminalFor |
P81938
|
FINISHED |
| Object | Ghaziabad |
—
|
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: Ghaziabad | Statement: [Shaheed Sthal, isMajorBusTerminalFor, Ghaziabad]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isMajorBusTerminalFor Context triple: [Shaheed Sthal, isMajorBusTerminalFor, Ghaziabad]
-
A.
isMainBusStationFor
chosen
Indicates that one bus station serves as the primary or central station for a particular area, network, or service.
-
B.
isMajorTransitPointFor
Indicates that a location serves as a primary hub or key node for the movement or transfer of people, goods, or vehicles within a transportation network.
-
C.
isMajorBusHub
Indicates that a location serves as a primary node in the bus network, with high connectivity and significant passenger or route volume.
-
D.
hasBusTerminalType
Indicates the specific category or type of bus terminal associated with an entity.
-
E.
isMajorTransitNode
Indicates that a location functions as a primary hub in a transportation network, where multiple major routes or services intersect or connect.
- 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_69fdd5fba5048190b7d430ae2054a1fd |
completed | May 8, 2026, 12:24 p.m. |
| PD | Predicate disambiguation | batch_69fdd35f76f88190a1854ea27132f9c7 |
completed | May 8, 2026, 12:13 p.m. |
Created at: May 3, 2026, 4:04 p.m.