Triple
T13844677
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wye Bridge |
E332764
|
entity |
| Predicate | isPartOfCrossing |
P47021
|
FINISHED |
| Object | original Severn Bridge crossing |
—
|
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: original Severn Bridge crossing | Statement: [Wye Bridge, isPartOfCrossing, original Severn Bridge crossing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPartOfCrossing Context triple: [Wye Bridge, isPartOfCrossing, original Severn Bridge crossing]
-
A.
crossingOf
chosen
Indicates that one entity serves as the intersection or crossing point of two or more linear features, such as roads, paths, or tracks.
-
B.
hasRailwayCrossing
Indicates that a location or route includes a point where a railway line and a road or path intersect, typically at the same level.
-
C.
isLocalCrossroads
Indicates that a location serves as a junction where multiple local routes or streets intersect.
-
D.
hasBridgeTypeCrossing
Indicates that a bridge is characterized by a specific type of crossing it provides or supports.
-
E.
hasMajorCrossing
Indicates that one entity has a significant or primary intersection or crossing with another entity.
- 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_69d81c5ba13c8190839315f54768acfd |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de02b1a25c8190a9f85ba43c421188 |
completed | April 14, 2026, 9:02 a.m. |
| PD | Predicate disambiguation | batch_69dbc8691b608190a25a7c70a366b170 |
completed | April 12, 2026, 4:29 p.m. |
Created at: April 9, 2026, 10:13 p.m.