Triple
T18801228
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Walterdale Bridge (Edmonton) |
E459755
|
entity |
| Predicate | replacesStructureFrom |
P10258
|
FINISHED |
| Object | 1913 |
—
|
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: 1913 | Statement: [Walterdale Bridge (Edmonton), replacesStructureFrom, 1913]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: replacesStructureFrom Context triple: [Walterdale Bridge (Edmonton), replacesStructureFrom, 1913]
-
A.
replacedStructure
chosen
Indicates that one structure has been substituted for, or taken the place of, another structure.
-
B.
replacedStructureType
Indicates that one structure type has been substituted or superseded by another structure type.
-
C.
replacedStructureDamagedBy
Indicates that a structure which has been replaced is (or was) damaged by a specified agent, event, or condition.
-
D.
reusesStructureOf
Indicates that one entity adopts or incorporates the structural design or organization of another entity.
-
E.
convertedStructure
Indicates that one structure has been transformed or converted into another structure.
- 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_69d8d398c7d4819091cb2f7e48948aeb |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e5a02332d88190b68feea7f2f86d06 |
completed | April 20, 2026, 3:40 a.m. |
| PD | Predicate disambiguation | batch_69e48d16dd34819096e096d0c0e4c15c |
completed | April 19, 2026, 8:06 a.m. |
Created at: April 10, 2026, 11:53 a.m.