Triple
T32214527
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | La Dibona |
E822891
|
entity |
| Predicate | standardRouteName |
P183138
|
FINISHED |
| Object | Voie Normale |
—
|
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: Voie Normale | Statement: [La Dibona, standardRouteName, Voie Normale]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: standardRouteName Context triple: [La Dibona, standardRouteName, Voie Normale]
-
A.
standardRouteStartsFrom
Indicates that a standard or predefined route has its starting point at a specified location or entity.
-
B.
standardRouteClass
Indicates that a route is classified according to a predefined standard category or class used for routing or transportation.
-
C.
standardRouteSide
Indicates the usual or designated side of a route on which something (e.g., traffic, walking, or placement) is expected to occur or be positioned.
-
D.
standardRouteGain
Indicates the amount of benefit, profit, or advantage obtained through following a normal or predefined route or process.
-
E.
onStandardRouteOf
Indicates that something lies along or follows the usual, predefined, or officially designated route of another entity.
- 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_69f3490a3bec819097bc58d4731b9d08 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f798387ea481909f51303f53a22e52 |
completed | May 3, 2026, 6:47 p.m. |
| PD | Predicate disambiguation | batch_69f7961550f88190b7bb8a9155458b54 |
completed | May 3, 2026, 6:38 p.m. |
| PDg | Predicate description generation | batch_69f79798663481908d6bc48dd6a94ca6 |
completed | May 3, 2026, 6:44 p.m. |
Created at: May 1, 2026, 12:37 a.m.