Triple
T31456111
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Connecticut parkways |
E802453
|
entity |
| Predicate | bridgeStyle |
P154237
|
FINISHED |
| Object | Art Deco bridges on some segments |
—
|
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: Art Deco bridges on some segments | Statement: [Connecticut parkways, bridgeStyle, Art Deco bridges on some segments]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bridgeStyle Context triple: [Connecticut parkways, bridgeStyle, Art Deco bridges on some segments]
-
A.
bridgeType
Indicates the specific kind or classification of a bridge associated with an entity.
-
B.
bridgesStyleBetween
Indicates a relationship where something connects or harmonizes two different styles, serving as a transitional or integrative link between them.
-
C.
hasBridgeStyle
chosen
Indicates that a bridge is characterized by a particular architectural or structural style.
-
D.
bridgeLocation
Indicates the specific place or area where a bridge is situated or spans.
-
E.
bridgeFeature
Indicates that one entity functions as a structural or functional feature of a bridge associated with another 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_69f348c678ac81908a2e950867619061 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6a5f71b2c8190aade8a83f465be0c |
completed | May 3, 2026, 1:33 a.m. |
| PD | Predicate disambiguation | batch_69f69fe66df08190958558d63ee623d9 |
completed | May 3, 2026, 1:07 a.m. |
Created at: April 30, 2026, 9:16 p.m.