Triple
T33665966
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Portal North Bridge project |
E862491
|
entity |
| Predicate | replacesStructureType |
P35568
|
FINISHED |
| Object | swing-span movable 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: swing-span movable bridge | Statement: [Portal North Bridge project, replacesStructureType, swing-span movable bridge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: replacesStructureType Context triple: [Portal North Bridge project, replacesStructureType, swing-span movable bridge]
-
A.
replacedStructureType
chosen
Indicates that one structure type has been substituted or superseded by another structure type.
-
B.
replacedStructure
Indicates that one structure has been substituted for, or taken the place of, another structure.
-
C.
originalStructureType
Indicates the type or category of the structure that an entity originally had before any changes or transformations.
-
D.
replacedStructureAtLocation
Indicates that one structure has been substituted for another at a specific location.
-
E.
replacedSurfaceType
Indicates that one surface type has been substituted or changed to another surface type.
- 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_69f34984c4008190bb82f33a7819da64 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fd82ed2a4c81908bd7797fbd2e3d08 |
completed | May 8, 2026, 6:30 a.m. |
| PD | Predicate disambiguation | batch_69fd814cc10481908e4f8123d35a5d0c |
completed | May 8, 2026, 6:23 a.m. |
Created at: May 1, 2026, 1:42 a.m.