Triple
T14279333
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Critérium du Dauphiné Libéré 1964 |
E354000
|
entity |
| Predicate | usesRoadType |
P1019
|
FINISHED |
| Object | public roads |
—
|
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: public roads | Statement: [Critérium du Dauphiné Libéré 1964, usesRoadType, public roads]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesRoadType Context triple: [Critérium du Dauphiné Libéré 1964, usesRoadType, public roads]
-
A.
roadUse
Indicates that an entity utilizes or travels on a particular road or roadway for movement or transport.
-
B.
hasRoadway
Indicates that one location or area is connected to another by a road or roadway infrastructure.
-
C.
roadType
chosen
Indicates the classification or category of a road based on its functional or physical characteristics.
-
D.
hasRoadNetworkType
Indicates the type or classification of road network associated with or present in an entity.
-
E.
onRoad
Indicates that one entity is located on, traveling along, or otherwise situated upon a road.
- 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_69d8278d25148190abf1a8c8f5f533ad |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de6585270c8190a717127b2f5dab3b |
completed | April 14, 2026, 4:04 p.m. |
| PD | Predicate disambiguation | batch_69de2a88446481909cd526da97a3b70f |
completed | April 14, 2026, 11:52 a.m. |
Created at: April 10, 2026, 1:10 a.m.