Triple
T34800795
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | London–Cardiff |
E1003212
|
entity |
| Predicate | hasMajorRoadRoute |
P385
|
FINISHED |
| Object | M4 motorway |
E55408
|
NE 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: M4 motorway | Statement: [London–Cardiff, hasMajorRoadRoute, M4 motorway]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMajorRoadRoute Context triple: [London–Cardiff, hasMajorRoadRoute, M4 motorway]
-
A.
isMajorRoadIn
Indicates that a road is classified as a major road within a specified geographic area or jurisdiction.
-
B.
hasMajorHighway
chosen
Indicates that a location or area is served by or directly connected to a major highway route.
-
C.
hasMajorRouteType
Indicates that an entity is associated with a primary classification of transportation route (such as highway, rail line, or other major route type).
-
D.
isMajorTrafficRoute
Indicates that a road or pathway serves as a primary, heavily used route for traffic flow within a transportation network.
-
E.
isMajorRouteThrough
Indicates that a route serves as a primary or significant pathway passing through a specified area or location.
- F. None of above.
Provenance (4 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_69f76db543808190b188c6c86a91491b |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_6a01c5c5dbb881909b19ba87a7760ee7 |
completed | May 11, 2026, 12:04 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a41710232788190b0219d22ff47f7d7 |
completed | June 28, 2026, 7:07 p.m. |
| PD | Predicate disambiguation | batch_6a01c549af98819098e0effd775b7710 |
completed | May 11, 2026, 12:02 p.m. |
Created at: May 3, 2026, 3:59 p.m.