Triple
T17837761
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Green Line (Hyderabad Metro) |
E445436
|
entity |
| Predicate | hasCorridorRole |
P45760
|
FINISHED |
| Object | main corridor of Hyderabad Metro |
—
|
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: main corridor of Hyderabad Metro | Statement: [Green Line (Hyderabad Metro), hasCorridorRole, main corridor of Hyderabad Metro]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCorridorRole Context triple: [Green Line (Hyderabad Metro), hasCorridorRole, main corridor of Hyderabad Metro]
-
A.
hasCorridor
Indicates that one entity includes, is connected by, or provides access through a corridor to another entity.
-
B.
corridorRole
chosen
Indicates a relationship where an entity functions as or is assigned the role of a corridor within a spatial or architectural context.
-
C.
hasCorridorName
Indicates that an entity is associated with or identified by the name of a specific corridor.
-
D.
hasEntranceRole
Indicates that an entity participates in an entrance or access point with a specific functional role or capacity.
-
E.
isPartOfCorridorSystem
Indicates that one entity forms a component or segment within a larger interconnected corridor system.
- 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_69d8b9f1a6d881909f024bc603111cdb |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e48d28c14881909033abd09bbdb135 |
completed | April 19, 2026, 8:07 a.m. |
| PD | Predicate disambiguation | batch_69e3d8e266888190ae976b4b7d5b886f |
completed | April 18, 2026, 7:17 p.m. |
Created at: April 10, 2026, 10:16 a.m.