Triple
T10449896
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sunshine Skyway Bridge |
E246391
|
entity |
| Predicate | replacedStructureDamagedBy |
P94100
|
FINISHED |
| Object | 1980 freighter collision |
—
|
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: 1980 freighter collision | Statement: [Sunshine Skyway Bridge, replacedStructureDamagedBy, 1980 freighter collision]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: replacedStructureDamagedBy Context triple: [Sunshine Skyway Bridge, replacedStructureDamagedBy, 1980 freighter collision]
-
A.
replacedStructure
Indicates that one structure has been substituted for, or taken the place of, another structure.
-
B.
affectedStructure
Indicates that one entity is the structure, component, or part that is impacted, altered, or influenced by another entity or event.
-
C.
replacedStructureType
Indicates that one structure type has been substituted or superseded by another structure type.
-
D.
damagedBy
Indicates that one entity has caused harm, impairment, or deterioration to another entity.
-
E.
damagedIn
Indicates that an entity has suffered harm, impairment, or destruction as a result of a specified event, process, or condition.
- 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_69d381c04fe08190957c26c526a3b05a |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4fe09af04819083db42f4de4cb0a9 |
completed | April 7, 2026, 12:52 p.m. |
| PD | Predicate disambiguation | batch_69d4fb73a5e48190a8df4775bc5da80f |
completed | April 7, 2026, 12:41 p.m. |
| PDg | Predicate description generation | batch_69d4fe058fcc81909428137d9ffd6d90 |
completed | April 7, 2026, 12:52 p.m. |
Created at: April 6, 2026, 12:17 p.m.