Triple
T34865953
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sir Leo Hielscher Bridges |
E1005008
|
entity |
| Predicate | secondBridgeOpened |
P71774
|
FINISHED |
| Object | 2010 |
—
|
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: 2010 | Statement: [Sir Leo Hielscher Bridges, secondBridgeOpened, 2010]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: secondBridgeOpened Context triple: [Sir Leo Hielscher Bridges, secondBridgeOpened, 2010]
-
A.
bridgeOpened
Indicates that a bridge has transitioned from a closed or inactive state to being open and available for use.
-
B.
originalBridgeOpened
Indicates that the first or initial version of a bridge was opened for use or put into operation.
-
C.
openedAsTollBridge
Indicates that a bridge was initially opened to traffic as a toll bridge, requiring users to pay a fee to cross.
-
D.
secondTunnelOpened
Indicates that a second tunnel has been opened and is now available for use in addition to an existing tunnel.
-
E.
secondSpanOpenedToTraffic
chosen
Indicates that a second span or section of a structure (such as a bridge) has been completed and officially made available for use by traffic.
- 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_69f76dbb678081909a247b9b5e1a73ac |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69ff289541e0819096eeceb8e6332650 |
completed | May 9, 2026, 12:29 p.m. |
| PD | Predicate disambiguation | batch_69ff281ab1988190920f0443be9f10cc |
completed | May 9, 2026, 12:27 p.m. |
Created at: May 3, 2026, 4 p.m.