Triple
T21359204
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vauxhall Bridge |
E526721
|
entity |
| Predicate | hasPreviousStructureOpened |
P14623
|
FINISHED |
| Object | 1816 |
—
|
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: 1816 | Statement: [Vauxhall Bridge, hasPreviousStructureOpened, 1816]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPreviousStructureOpened Context triple: [Vauxhall Bridge, hasPreviousStructureOpened, 1816]
-
A.
hasStructureHistory
Indicates that there exists a record or account detailing the past states, changes, or development of a structure over time.
-
B.
previouslyOpenedTo
Indicates that an entity had been accessible or available to another entity at some earlier time in the past.
-
C.
previousStructure
chosen
Indicates that one structure directly precedes another in a defined sequence or configuration.
-
D.
hasStructureAbove
Indicates that one entity has another entity positioned vertically higher or located on top of it within a structural or spatial arrangement.
-
E.
hasEnclosedStructure
Indicates that one entity possesses or contains another entity within a surrounding or enclosing 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_69e0b51d8a308190b09113b3b3f9bc15 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69ee5bac9e1481909121e89f046c77f6 |
completed | April 26, 2026, 6:38 p.m. |
| PD | Predicate disambiguation | batch_69e6162bbfc88190a3e75859941b2638 |
completed | April 20, 2026, 12:03 p.m. |
Created at: April 16, 2026, 5:07 p.m.