Triple
T1092180
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eastern Parkway Line |
E24189
|
entity |
| Predicate | rightOfWayType |
P9536
|
FINISHED |
| Object | underground |
—
|
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: underground | Statement: [Eastern Parkway Line, rightOfWayType, underground]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rightOfWayType Context triple: [Eastern Parkway Line, rightOfWayType, underground]
-
A.
roadType
Indicates the classification or category of a road based on its functional or physical characteristics.
-
B.
roadFeature
Indicates that an entity is a specific physical or functional characteristic associated with a road, such as its structure, markings, or related infrastructure.
-
C.
someRightOfWayUsedBy
Indicates that a particular right of way is utilized or traversed by a specified user, route, or transport entity.
-
D.
crossingType
Indicates the specific kind or category of crossing (e.g., how or where one thing passes over, through, or across another).
-
E.
guidewayType
chosen
Indicates the specific kind or classification of guideway used in a transportation or movement 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_69a49404428c819092dcc9632f5f7b8b |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4b982018481908b222df095e318c0 |
completed | March 1, 2026, 10:11 p.m. |
| PD | Predicate disambiguation | batch_69a4b741b0cc8190be001a16a81f6d9e |
completed | March 1, 2026, 10:01 p.m. |
Created at: March 1, 2026, 7:42 p.m.