Triple
T2415595
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mersey Gateway Bridge |
E52293
|
entity |
| Predicate | hasApproachViaducts |
P17088
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Mersey Gateway Bridge, hasApproachViaducts, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasApproachViaducts Context triple: [Mersey Gateway Bridge, hasApproachViaducts, yes]
-
A.
hasViaduct
chosen
Indicates that one entity possesses, includes, or is connected by a viaduct in relation to another entity.
-
B.
hasApproachRoad
Indicates that one entity is connected to or accessed by another entity via an approach road leading to it.
-
C.
hasPassengerBridge
Indicates that one entity is connected to another by a bridge or walkway specifically designed for passengers to move between them.
-
D.
hasNumberOfBridges
Indicates the quantitative relationship specifying how many bridges are associated with a given entity.
-
E.
hasBridgeTo
Indicates that one entity is connected to another by a bridge or bridging structure that allows passage or linkage between them.
- 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_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. |
Created at: March 6, 2026, 9:41 p.m.