Triple
T2050684
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | London Bridge |
E45558
|
entity |
| Predicate | replacedStructureType |
P35568
|
FINISHED |
| Object | stone arch 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: stone arch bridge | Statement: [London Bridge, replacedStructureType, stone arch bridge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: replacedStructureType Context triple: [London Bridge, replacedStructureType, stone arch bridge]
-
A.
replacedStructure
Indicates that one structure has been substituted for, or taken the place of, another structure.
-
B.
replacedStructureOpened
Indicates that a previously existing structure has been removed or superseded and the new replacement structure has been opened or put into service.
-
C.
convertedStructure
Indicates that one structure has been transformed or converted into another structure.
-
D.
convertedStructureUse
Indicates that an entity’s original structural use has been changed to a different use or function.
-
E.
replacedWith
Indicates that one entity has been substituted or superseded by another entity, taking over its role, function, or position.
- F. None of above. chosen
Provenance (4 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_69a8891948208190ab7898da21824c77 |
completed | March 4, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69abb98f5f4881908d9aa0f10be44041 |
completed | March 7, 2026, 5:37 a.m. |
| PD | Predicate disambiguation | batch_69abb7abba508190b872f345d3ba51bb |
completed | March 7, 2026, 5:29 a.m. |
| PDg | Predicate description generation | batch_69abb94ec400819097596732aabed854 |
completed | March 7, 2026, 5:36 a.m. |
Created at: March 4, 2026, 7:39 p.m.