Triple
T9638388
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pensacola Bay Bridge |
E232993
|
entity |
| Predicate | temporarilyClosed |
P12551
|
FINISHED |
| Object | 2020 |
—
|
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: 2020 | Statement: [Pensacola Bay Bridge, temporarilyClosed, 2020]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: temporarilyClosed Context triple: [Pensacola Bay Bridge, temporarilyClosed, 2020]
-
A.
temporarilyClosedFrom
Indicates that an entity is not accessible or operating for a specific, limited time period starting from a given point.
-
B.
closedFor
Indicates that an entity is not available or accessible for use, entry, or operation during a specified time, condition, or reason.
-
C.
closedDuring
chosen
Indicates that an entity is not open or available for use during a specified time period or under certain conditions.
-
D.
closedVenue
Indicates that a venue is not open or available for use during a given time or event.
-
E.
openPitClosedIn
Indicates that an open-pit mine or excavation has been closed, decommissioned, or otherwise taken out of active use at a specified time or under specified conditions.
- 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_69ca848a5a908190aad251f4137b0c3a |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9b51b08081908e30744607b28953 |
completed | April 1, 2026, 10:25 p.m. |
| PD | Predicate disambiguation | batch_69ccd5acfa5c8190aaba3cf548723604 |
completed | April 1, 2026, 8:22 a.m. |
Created at: March 30, 2026, 8:11 p.m.