Triple
T2457304
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Strait of Messina |
E54451
|
entity |
| Predicate | bridgeProposalStatus |
P13063
|
FINISHED |
| Object | not built as of 2024 |
—
|
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: not built as of 2024 | Statement: [Strait of Messina, bridgeProposalStatus, not built as of 2024]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bridgeProposalStatus Context triple: [Strait of Messina, bridgeProposalStatus, not built as of 2024]
-
A.
bridgeName
Indicates the designated name assigned to a specific bridge.
-
B.
hasProposedOutcome
chosen
Indicates that an action, decision, or process is associated with a suggested or anticipated result that is being put forward but not yet realized or confirmed.
-
C.
bridgeUsed
Indicates that a bridge is utilized or traversed by an entity to cross between two locations or points.
-
D.
bridgeLocation
Indicates the specific place or area where a bridge is situated or spans.
-
E.
proposalProcess
Indicates the process or sequence of actions involved in creating, submitting, reviewing, and deciding on a proposal between entities.
- 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_69ab49dee84c819096b50a0049c347ac |
completed | March 6, 2026, 9:40 p.m. |
| NER | Named-entity recognition | batch_69abd49c5aa081909ab4f726a458b77f |
completed | March 7, 2026, 7:32 a.m. |
| PD | Predicate disambiguation | batch_69abd0b199488190aa381b36593ae1ac |
completed | March 7, 2026, 7:16 a.m. |
Created at: March 6, 2026, 9:44 p.m.