Triple
T19531137
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A10 |
E488654
|
entity |
| Predicate | hasRingRoadType |
P136665
|
FINISHED |
| Object | orbital motorway |
—
|
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: orbital motorway | Statement: [A10, hasRingRoadType, orbital motorway]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRingRoadType Context triple: [A10, hasRingRoadType, orbital motorway]
-
A.
hasRingRoadRole
Indicates that an entity has a specific functional role or responsibility in relation to a ring road.
-
B.
hasRingRoadLengthApproxKm
Indicates that an entity has a ring road whose length is approximately a specified number of kilometers.
-
C.
primaryRingRoad
Indicates that a road functions as the main circumferential or loop route encircling or bypassing a central area in a transport network.
-
D.
hasRoadNetworkType
Indicates the type or classification of road network associated with or present in an entity.
-
E.
hasArterialRoad
Indicates that one location or area is connected to or served by a major arterial road used for primary traffic flow.
- F. None of above. chosen
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_69d8e8db5b6c8190984b61f91981f575 |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e6363ec6cc8190b9e9ac0196b288f9 |
completed | April 20, 2026, 2:20 p.m. |
| PD | Predicate disambiguation | batch_69e514c9c00481909b76bda67957e58b |
completed | April 19, 2026, 5:45 p.m. |
| PDg | Predicate description generation | batch_69e51a23300c8190988552491d9783d7 |
completed | April 19, 2026, 6:08 p.m. |
Created at: April 10, 2026, 1:41 p.m.