Triple
T14249452
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Miyapur |
E353218
|
entity |
| Predicate | metroRole |
P29465
|
FINISHED |
| Object | terminal station on Red Line |
—
|
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: terminal station on Red Line | Statement: [Miyapur, metroRole, terminal station on Red Line]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: metroRole Context triple: [Miyapur, metroRole, terminal station on Red Line]
-
A.
hasPublicTransitRole
chosen
Indicates that an entity holds a specific functional role or responsibility within a public transit system.
-
B.
metropole
Indicates a relationship where one place functions as the principal or most important city or center of activity for another place or region.
-
C.
metroSystemColor
Indicates the color assigned to a metro or subway line within a transit system.
-
D.
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.
-
E.
subwayStation
Indicates that one entity is a subway station associated with, located in, or serving the other entity.
- 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_69d8278c43e08190824146f4632b89a5 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de6295ef9081909cfb0c1283bca21a |
completed | April 14, 2026, 3:51 p.m. |
| PD | Predicate disambiguation | batch_69de05c09b7881908acbca18bd7d997c |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 10, 2026, 1:08 a.m.