Triple
T22378740
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | William Cullen Bryant Viaduct vicinity |
E553213
|
entity |
| Predicate | roadTypeInArea |
P1777
|
FINISHED |
| Object | viaduct |
—
|
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: viaduct | Statement: [William Cullen Bryant Viaduct vicinity, roadTypeInArea, viaduct]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roadTypeInArea Context triple: [William Cullen Bryant Viaduct vicinity, roadTypeInArea, viaduct]
-
A.
roadType
Indicates the classification or category of a road based on its functional or physical characteristics.
-
B.
roadSystem
Indicates a relationship where multiple roads are organized and connected as part of a larger, integrated transportation network or infrastructure.
-
C.
roadFeature
chosen
Indicates that an entity is a specific physical or functional characteristic associated with a road, such as its structure, markings, or related infrastructure.
-
D.
roadPassType
Indicates the type or category of permission or authorization required to use or pass along a particular road or route.
-
E.
roadMode
Indicates the mode or type of transportation being used on a road within the described relationship or action.
- 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_69e11e4c03248190a26a5060ea6973ee |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f1582a04ac81908d4d389b150be7f1 |
completed | April 29, 2026, 1 a.m. |
| PD | Predicate disambiguation | batch_69e73011e6388190a05edf137f488441 |
completed | April 21, 2026, 8:06 a.m. |
Created at: April 16, 2026, 8:45 p.m.