Triple
T9866828
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Port Mann Bridge |
E239853
|
entity |
| Predicate | previousStructureType |
P35487
|
FINISHED |
| Object | steel arch truss bridge |
—
|
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: steel arch truss bridge | Statement: [Port Mann Bridge, previousStructureType, steel arch truss bridge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: previousStructureType Context triple: [Port Mann Bridge, previousStructureType, steel arch truss bridge]
-
A.
previousStructure
Indicates that one structure directly precedes another in a defined sequence or configuration.
-
B.
originalStructureType
chosen
Indicates the type or category of the structure that an entity originally had before any changes or transformations.
-
C.
currentStructure
Indicates that an entity is the present or active structural configuration or organization associated with another entity.
-
D.
usedStructure
Indicates that one entity makes use of, relies on, or operates through a particular structure (physical, logical, or organizational) to perform its function or action.
-
E.
designedStructureType
Indicates the type or category of structure that something has been specifically designed to be.
- 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.