Triple
T31219334
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A219 |
E795960
|
entity |
| Predicate | linksLocalTrafficTo |
P92991
|
FINISHED |
| Object | A40 Westway |
—
|
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: A40 Westway | Statement: [A219, linksLocalTrafficTo, A40 Westway]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: linksLocalTrafficTo Context triple: [A219, linksLocalTrafficTo, A40 Westway]
-
A.
servesLocalTraffic
chosen
Indicates that something (such as a road, route, or service) is primarily intended to accommodate or support traffic originating from or destined to nearby or surrounding areas rather than long-distance or through traffic.
-
B.
sharesTrafficWith
Indicates that two entities experience or contribute to overlapping or mutually affecting traffic flows.
-
C.
linkedNetwork
Indicates that two entities are connected through a shared or associated network relationship.
-
D.
linkedLocation
Indicates that one location is associated or connected to another location in a meaningful way, such as being related, referenced, or contextually tied.
-
E.
connectsLocation
Indicates a relationship where one entity serves as a link or route that joins or provides access between two locations.
- 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_69f224d9d52c8190a61f68ded37fa755 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69c4ba1c4819080ebeaddb6c16075 |
completed | May 3, 2026, 12:52 a.m. |
| PD | Predicate disambiguation | batch_69f696673214819094350e1d2648ef34 |
completed | May 3, 2026, 12:27 a.m. |
Created at: April 29, 2026, 9:10 p.m.