Triple
T22295318
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A36 motorway (Portugal) |
E551101
|
entity |
| Predicate | ringRoadRole |
P94212
|
FINISHED |
| Object | outer orbital route for Lisbon |
—
|
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: outer orbital route for Lisbon | Statement: [A36 motorway (Portugal), ringRoadRole, outer orbital route for Lisbon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ringRoadRole Context triple: [A36 motorway (Portugal), ringRoadRole, outer orbital route for Lisbon]
-
A.
hasRingRoadRole
chosen
Indicates that an entity has a specific functional role or responsibility in relation to a ring road.
-
B.
roadSystemRole
Indicates the specific functional role or responsibility an entity has within a road or transportation network system.
-
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.
hasRingRoadType
Indicates that an entity is associated with a specific type or classification of ring road.
-
E.
routeRole
Indicates the specific functional role or purpose that an entity has within a particular route or path.
- 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_69e11e45fb848190a1b2ae21296e3a5f |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f1571fe76c8190a40b3679802a5475 |
completed | April 29, 2026, 12:56 a.m. |
| PD | Predicate disambiguation | batch_69e72ffa438481908f80879aef2a589b |
completed | April 21, 2026, 8:06 a.m. |
Created at: April 16, 2026, 8:41 p.m.