Triple
T34977317
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Villeblevin |
E1008715
|
entity |
| Predicate | roadPassingThrough |
P30397
|
FINISHED |
| Object | Route nationale 5 (historic) |
—
|
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: Route nationale 5 (historic) | Statement: [Villeblevin, roadPassingThrough, Route nationale 5 (historic)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roadPassingThrough Context triple: [Villeblevin, roadPassingThrough, Route nationale 5 (historic)]
-
A.
roadTraverses
chosen
Indicates that a road passes through, crosses, or extends across a specified geographic area or feature.
-
B.
roadPassType
Indicates the type or category of permission or authorization required to use or pass along a particular road or route.
-
C.
roadFeature
Indicates that an entity is a specific physical or functional characteristic associated with a road, such as its structure, markings, or related infrastructure.
-
D.
roadSystem
Indicates a relationship where multiple roads are organized and connected as part of a larger, integrated transportation network or infrastructure.
-
E.
roadAccessVia
Indicates that one location or area is reachable from another specifically by using a particular road or road segment.
- 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_69f76dc844a48190881951fffb83d17e |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78710282c81909146dc0be91e983f |
completed | May 3, 2026, 5:34 p.m. |
| PD | Predicate disambiguation | batch_69f784162134819098413482ef52042f |
completed | May 3, 2026, 5:21 p.m. |
Created at: May 3, 2026, 4:01 p.m.