Triple
T34294953
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arland Dean Williams Jr. |
E879998
|
entity |
| Predicate | bridgeNamedAfter |
P178861
|
FINISHED |
| Object | Arland D. Williams Jr. Memorial Bridge |
—
|
NE NERFINISHED |
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: Arland D. Williams Jr. Memorial Bridge | Statement: [Arland Dean Williams Jr., bridgeNamedAfter, Arland D. Williams Jr. Memorial Bridge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bridgeNamedAfter Context triple: [Arland Dean Williams Jr., bridgeNamedAfter, Arland D. Williams Jr. Memorial Bridge]
-
A.
bridgeName
Indicates the designated name assigned to a specific bridge.
-
B.
bridgeNickname
Indicates that one entity is an alternative or informal nickname used to refer to another entity, serving as a bridge between different name forms.
-
C.
bridgeLocation
Indicates the specific place or area where a bridge is situated or spans.
-
D.
bridgeFeature
Indicates that one entity functions as a structural or functional feature of a bridge associated with another entity.
-
E.
bridgeType
Indicates the specific kind or classification of a bridge associated with an entity.
- 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_69f349b6df1c81908e5e5b6c2ab6409b |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f717836f0c8190b4a397bbac37dd09 |
completed | May 3, 2026, 9:38 a.m. |
| PD | Predicate disambiguation | batch_69f7127a2ff08190b77d00963c9df621 |
completed | May 3, 2026, 9:16 a.m. |
| PDg | Predicate description generation | batch_69f71782422c81908196d5e4a610cb1a |
completed | May 3, 2026, 9:38 a.m. |
Created at: May 1, 2026, 1:57 a.m.