Triple
T23864353
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wilbur Cross Parkway |
E592534
|
entity |
| Predicate | hasBridgeStyle |
P154237
|
FINISHED |
| Object | stone-faced bridges |
—
|
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: stone-faced bridges | Statement: [Wilbur Cross Parkway, hasBridgeStyle, stone-faced bridges]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBridgeStyle Context triple: [Wilbur Cross Parkway, hasBridgeStyle, stone-faced bridges]
-
A.
hasBridgeTo
Indicates that one entity is connected to another by a bridge or bridging structure that allows passage or linkage between them.
-
B.
hasBridgeView
Indicates that one entity provides a view of, or overlooking, a bridge from its location or perspective.
-
C.
hasBridgeSection
Indicates that one entity includes or is associated with a specific bridge section as a distinct part or component.
-
D.
bridgesStyleBetween
Indicates a relationship where something connects or harmonizes two different styles, serving as a transitional or integrative link between them.
-
E.
hasBridgeLayer
Indicates that one entity includes or is associated with a specific bridge layer within its structure or configuration.
- F. None of above. chosen
Provenance (4 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_69e25d22eb488190914b193aff952e83 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1cae22ff08190b7085cae21938bb4 |
completed | April 29, 2026, 9:09 a.m. |
| PD | Predicate disambiguation | batch_69f1614a65a88190bde1efb368a151e4 |
completed | April 29, 2026, 1:39 a.m. |
| PDg | Predicate description generation | batch_69f16e348b548190b76e50f9b611f76d |
completed | April 29, 2026, 2:34 a.m. |
Created at: April 17, 2026, 8:13 p.m.