Triple
T2415587
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mersey Gateway Bridge |
E52293
|
entity |
| Predicate | hasCentralPylonHeight |
P37776
|
FINISHED |
| Object | 125 metres (approximate) |
—
|
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: 125 metres (approximate) | Statement: [Mersey Gateway Bridge, hasCentralPylonHeight, 125 metres (approximate)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCentralPylonHeight Context triple: [Mersey Gateway Bridge, hasCentralPylonHeight, 125 metres (approximate)]
-
A.
hasPylon
Indicates that one entity possesses, includes, or is equipped with a pylon as part of its structure or configuration.
-
B.
hasTowerHeight
Indicates that an entity (such as a tower or structure) has a specific height value associated with it.
-
C.
centralArchHeight
Indicates the vertical height of the central arch in a structure relative to a reference level.
-
D.
heightWithPedestal
Indicates the total vertical measurement of an object including the height of its supporting pedestal.
-
E.
hasCentralSection
Indicates that an entity possesses a distinct middle or central part within its overall structure or composition.
- 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_69ab495622948190bc6bc6e4cddaf645 |
completed | March 6, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69abc94d048481908409d60129aef747 |
completed | March 7, 2026, 6:44 a.m. |
| PD | Predicate disambiguation | batch_69abc5a6cbd0819086c0716e266b7ebb |
completed | March 7, 2026, 6:28 a.m. |
| PDg | Predicate description generation | batch_69abc6011e348190b6f9c038c7559289 |
completed | March 7, 2026, 6:30 a.m. |
Created at: March 6, 2026, 9:41 p.m.