Triple
T38650977
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Frisco Bridge |
E939743
|
entity |
| Predicate | wasAtTime |
P191329
|
FINISHED |
| Object | one of the longest steel truss bridges in the United States |
—
|
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: one of the longest steel truss bridges in the United States | Statement: [Frisco Bridge, wasAtTime, one of the longest steel truss bridges in the United States]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasAtTime Context triple: [Frisco Bridge, wasAtTime, one of the longest steel truss bridges in the United States]
-
A.
wasPerformedAt
Indicates that an action or event took place at a specific location or venue.
-
B.
wasIn
Indicates that an entity existed, occurred, or was located within a particular place or context during a specified time or situation.
-
C.
locatedInTimeBefore
Indicates that one temporal event or interval occurs entirely before another in time.
-
D.
wasInForceDuring
Indicates that a rule, law, agreement, or other normative provision was legally valid and operative throughout a specified time period.
-
E.
tookPlaceAfter
Indicates that one event or occurrence happened later in time than another event or occurrence.
- 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_69f76ede49648190a48bfe47032a05a3 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcdb0de8c08190928cd1323f80ab5c |
completed | May 7, 2026, 6:33 p.m. |
| PD | Predicate disambiguation | batch_69fcd9017dd88190b32a73fe78909740 |
completed | May 7, 2026, 6:25 p.m. |
| PDg | Predicate description generation | batch_69fcdb0cf6008190b27046b694f84356 |
completed | May 7, 2026, 6:33 p.m. |
Created at: May 3, 2026, 4:33 p.m.