Triple
T1325134
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Forth Bridge (rail, south end) |
E28308
|
entity |
| Predicate | connectsDirection |
P4069
|
FINISHED |
| Object | northbound traffic over Forth Bridge |
—
|
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: northbound traffic over Forth Bridge | Statement: [Forth Bridge (rail, south end), connectsDirection, northbound traffic over Forth Bridge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: connectsDirection Context triple: [Forth Bridge (rail, south end), connectsDirection, northbound traffic over Forth Bridge]
-
A.
connectsTo
Indicates a relationship where one entity is linked or joined to another, allowing interaction, communication, or transfer between them.
-
B.
containsDirectionOf
Indicates that one entity includes or encompasses the directional orientation or path associated with another entity.
-
C.
connectsArea
Indicates that one area serves as a link or passage between two other areas, enabling movement or interaction between them.
-
D.
transportDirection
Indicates the directional flow or route along which something is transported from an origin toward a destination.
-
E.
hasTrafficDirection
chosen
Indicates that there is a specified flow or orientation of traffic associated with an entity (such as a road, lane, or route).
- 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_69a498540a2481909e807a762280d3ba |
completed | March 1, 2026, 7:49 p.m. |
| NER | Named-entity recognition | batch_69a4c19e81c0819092f85201ae34422a |
completed | March 1, 2026, 10:45 p.m. |
| PD | Predicate disambiguation | batch_69a4beedb49c8190beb5b85cdda05013 |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:55 p.m.