Triple
T18275433
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hisingsbron |
E437721
|
entity |
| Predicate | replacedStructureLocation |
P10258
|
FINISHED |
| Object | site of former Götaälvbron |
—
|
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: site of former Götaälvbron | Statement: [Hisingsbron, replacedStructureLocation, site of former Götaälvbron]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: replacedStructureLocation Context triple: [Hisingsbron, replacedStructureLocation, site of former Götaälvbron]
-
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.
replacedStructureOpened
Indicates that a previously existing structure has been removed or superseded and the new replacement structure has been opened or put into service.
-
D.
replacedStructureDamagedBy
Indicates that a structure which has been replaced is (or was) damaged by a specified agent, event, or condition.
-
E.
placedBy
Indicates that one entity was positioned, set, or put in a location or context by another entity.
- 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_69d8b914530c8190b4474d862a2b2a1b |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e50051bccc8190832eacdb6945d6b7 |
completed | April 19, 2026, 4:18 p.m. |
| PD | Predicate disambiguation | batch_69e44fd81c788190b08c6be3b07a08c5 |
completed | April 19, 2026, 3:45 a.m. |
Created at: April 10, 2026, 10:34 a.m.