Triple
T38380206
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | D909 |
E893737
|
entity |
| Predicate | hasRoadDesignationSystem |
P99654
|
FINISHED |
| Object | D-road system of France |
—
|
NE NERFINISHED |
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: D-road system of France | Statement: [D909, hasRoadDesignationSystem, D-road system of France]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRoadDesignationSystem Context triple: [D909, hasRoadDesignationSystem, D-road system of France]
-
A.
hasRoadNumberSystem
chosen
Indicates that a place or region uses a specific system for assigning numbers to its roads or highways.
-
B.
stateRouteDesignation
Indicates the specific state-level route number or designation assigned to a roadway within a state highway system.
-
C.
routeDesignationOf
Indicates that one entity is the official route number, code, or designation assigned to another entity representing a transportation route.
-
D.
hasAssociatedRoadSystem
Indicates that one entity is linked to, or served by, a particular road or roadway network.
-
E.
roadSystem
Indicates a relationship where multiple roads are organized and connected as part of a larger, integrated transportation network or infrastructure.
- 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_69f76e4b1f748190a380696a16eae4a2 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69ff109695008190a22b47ef8be2e3f9 |
completed | May 9, 2026, 10:46 a.m. |
| PD | Predicate disambiguation | batch_69ff0f243ea88190970d2c520b55c816 |
completed | May 9, 2026, 10:40 a.m. |
Created at: May 3, 2026, 4:31 p.m.