Triple
T9866837
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Port Mann Bridge |
E239853
|
entity |
| Predicate | openedFullyCompletedConfiguration |
P62160
|
FINISHED |
| Object | 2015 |
—
|
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: 2015 | Statement: [Port Mann Bridge, openedFullyCompletedConfiguration, 2015]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openedFullyCompletedConfiguration Context triple: [Port Mann Bridge, openedFullyCompletedConfiguration, 2015]
-
A.
fullOpeningCompleted
chosen
Indicates that the action or process of fully opening something has been completed.
-
B.
openedAfter
Indicates that one entity was opened at a later time than another entity.
-
C.
openedComponent
Indicates that one entity has caused another entity (typically a component or part of a system) to transition from a closed or inactive state to an open or active state.
-
D.
openedInStages
Indicates that the opening or launch of something occurred in multiple distinct phases or stages rather than all at once.
-
E.
openedAsComplex
Indicates that one entity was inaugurated or began operation specifically as a multi-part or multi-use complex, rather than as a single standalone facility.
- 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_69ca84e7506c819095cbde4ff16512bb |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cdb3d209ac8190b9bc9ff017a132da |
completed | April 2, 2026, 12:09 a.m. |
| PD | Predicate disambiguation | batch_69cd1d7621d48190aa6a6f34399514b0 |
completed | April 1, 2026, 1:28 p.m. |
Created at: March 30, 2026, 8:36 p.m.