Triple
T24661751
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A90 |
E610554
|
entity |
| Predicate | openedAsRingRoad |
P157166
|
FINISHED |
| Object | 20th century |
—
|
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: 20th century | Statement: [A90, openedAsRingRoad, 20th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openedAsRingRoad Context triple: [A90, openedAsRingRoad, 20th century]
-
A.
primaryRingRoad
Indicates that a road functions as the main circumferential or loop route encircling or bypassing a central area in a transport network.
-
B.
hasRingRoadRole
Indicates that an entity has a specific functional role or responsibility in relation to a ring road.
-
C.
hasRingRoadType
Indicates that an entity is associated with a specific type or classification of ring road.
-
D.
openedAsMotorway
Indicates that a road segment was initially opened to traffic specifically as a motorway.
-
E.
openedAsTollBridge
Indicates that a bridge was initially opened to traffic as a toll bridge, requiring users to pay a fee to cross.
- 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_69e2c4d453248190a020354e93ef6282 |
completed | April 17, 2026, 11:40 p.m. |
| NER | Named-entity recognition | batch_69f422aee0408190899efe7e24ef2b40 |
completed | May 1, 2026, 3:49 a.m. |
| PD | Predicate disambiguation | batch_69f420e92cc88190a803aecdae78a051 |
completed | May 1, 2026, 3:41 a.m. |
| PDg | Predicate description generation | batch_69f422add8508190a76e56cfa756eeb8 |
completed | May 1, 2026, 3:49 a.m. |
Created at: April 18, 2026, 2:34 a.m.