Triple
T31838579
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brigg railway station |
E812736
|
entity |
| Predicate | hasFreightTrafficNearby |
P96747
|
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: [Brigg railway station, hasFreightTrafficNearby, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFreightTrafficNearby Context triple: [Brigg railway station, hasFreightTrafficNearby, yes]
-
A.
hasTruckTraffic
Indicates that there is truck-related vehicular movement or flow occurring on or through a specified location or route.
-
B.
hasHeavyTraffic
Indicates that a location, route, or area is experiencing a high volume of traffic, causing congestion or delays.
-
C.
hasTransportationProximityTo
Indicates that one entity is located near or conveniently accessible to another entity in terms of transportation options or routes.
-
D.
hasNearbyTransportationCorridor
chosen
Indicates that an entity is located close to a significant transportation route or corridor, such as a road, railway, or transit line.
-
E.
hasNearbyShippingLane
Indicates that there is a shipping lane located close to the referenced entity or area.
- 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_69f348ea7ffc8190a2ab43d80277cf59 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f739a638748190808e7a2930dce16e |
completed | May 3, 2026, 12:03 p.m. |
| PD | Predicate disambiguation | batch_69f732f2dc6c8190a4e86da98cc5eb05 |
completed | May 3, 2026, 11:35 a.m. |
Created at: April 30, 2026, 11:48 p.m.