Triple
T2906011
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1940 Tacoma Narrows Bridge |
E62764
|
entity |
| Predicate | collapsedOn |
P42652
|
FINISHED |
| Object | November 7, 1940 |
—
|
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: November 7, 1940 | Statement: [1940 Tacoma Narrows Bridge, collapsedOn, November 7, 1940]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: collapsedOn Context triple: [1940 Tacoma Narrows Bridge, collapsedOn, November 7, 1940]
-
A.
collapsedAfter
Indicates that one entity collapsed at some point in time after another specified event or entity’s collapse.
-
B.
collapsedDuring
Indicates that one entity structurally failed or fell down while another specified event or process was occurring.
-
C.
collapsedWith
Indicates that one entity fell down or caved in together with another entity, typically as part of the same collapse event.
-
D.
closed
Indicates that an entity has brought something (such as an object, container, or space) from an open state into a shut or sealed state, or that it is currently in that shut state.
-
E.
closedIn
Indicates that one entity is enclosed, contained, or surrounded within the boundaries or limits defined by another 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_69ab4c3e070c8190b78d3d2c005876dd |
completed | March 6, 2026, 9:50 p.m. |
| NER | Named-entity recognition | batch_69abe0cee7988190875665145c3cd605 |
completed | March 7, 2026, 8:24 a.m. |
| PD | Predicate disambiguation | batch_69abdd19bac881908f047d616aca8438 |
completed | March 7, 2026, 8:08 a.m. |
| PDg | Predicate description generation | batch_69abdd96670c8190b727f9ac27dadf67 |
completed | March 7, 2026, 8:11 a.m. |
Created at: March 6, 2026, 10:11 p.m.