Triple
T3489862
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | M58 motorway |
E73698
|
entity |
| Predicate | hasBridgeOrStructure |
P48693
|
FINISHED |
| Object | bridges over local roads and railways |
—
|
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: bridges over local roads and railways | Statement: [M58 motorway, hasBridgeOrStructure, bridges over local roads and railways]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBridgeOrStructure Context triple: [M58 motorway, hasBridgeOrStructure, bridges over local roads and railways]
-
A.
hasBridgeTunnel
Indicates that there exists a bridge or tunnel connection between two locations or structures.
-
B.
hasBridgeTo
Indicates that one entity is connected to another by a bridge or bridging structure that allows passage or linkage between them.
-
C.
hasMajorBridge
Indicates that one entity possesses or includes a primary or significant bridge associated with it.
-
D.
hasBridgeSection
Indicates that one entity includes or is associated with a specific bridge section as a distinct part or component.
-
E.
hasBridgeTypeCrossing
Indicates that a bridge is characterized by a specific type of crossing it provides or supports.
- 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_69ad85cca8d4819088494e9f3340fab5 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adbb94190c8190a81eb41042e51a00 |
completed | March 8, 2026, 6:10 p.m. |
| PD | Predicate disambiguation | batch_69adae0b34908190b2bb5766a2231f7a |
completed | March 8, 2026, 5:12 p.m. |
| PDg | Predicate description generation | batch_69adb055ed2481908171effe28151cf9 |
completed | March 8, 2026, 5:22 p.m. |
Created at: March 8, 2026, 3:18 p.m.