Triple
T33120881
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | M4 motorway |
E847591
|
entity |
| Predicate | formerCrossingVia |
P190525
|
FINISHED |
| Object | Severn Bridge |
—
|
NE NERFINISHED |
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: Severn Bridge | Statement: [M4 motorway, formerCrossingVia, Severn Bridge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formerCrossingVia Context triple: [M4 motorway, formerCrossingVia, Severn Bridge]
-
A.
crossingOf
Indicates that one entity serves as the intersection or crossing point of two or more linear features, such as roads, paths, or tracks.
-
B.
crossedBy
Indicates that one entity (typically a path, line, or boundary) is intersected or traversed by another entity.
-
C.
crossingUsedBy
chosen
Indicates that a particular crossing (such as a road, rail, or pedestrian crossing) is utilized or traversed by a specified user or traffic flow.
-
D.
crossedFrom
Indicates that an entity moved across a boundary or dividing line starting from a specified origin location or side.
-
E.
attemptedCrossingBy
Indicates that an entity made an effort to cross or traverse another entity, regardless of whether the crossing was successful.
- 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_69f3495751a081909850af5843da40dc |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69ffab5adf2c819084700c5ea34615bf |
completed | May 9, 2026, 9:47 p.m. |
| PD | Predicate disambiguation | batch_69ffaabffa208190b5214ca17cc8a5ea |
completed | May 9, 2026, 9:44 p.m. |
Created at: May 1, 2026, 1:27 a.m.