Triple
T10371923
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Valence, Drôme |
E244403
|
entity |
| Predicate | distanceToLyonKilometers |
P74121
|
FINISHED |
| Object | approximately 100 |
—
|
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: approximately 100 | Statement: [Valence, Drôme, distanceToLyonKilometers, approximately 100]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToLyonKilometers Context triple: [Valence, Drôme, distanceToLyonKilometers, approximately 100]
-
A.
distanceFromLyon
chosen
Indicates the spatial distance between a given entity and the city of Lyon.
-
B.
distanceFromParisGareDeLyon
Indicates the distance between an entity and Paris Gare de Lyon railway station.
-
C.
distanceToMarseilleKilometers
Indicates the physical distance, measured in kilometers, between a given location or entity and the city of Marseille.
-
D.
distanceFromFoixKilometres
Indicates the physical distance, measured in kilometers, between a given place or entity and the location of Foix.
-
E.
distanceFromBesançonKilometres
Indicates the distance, measured in kilometers, between an entity and the city of Besançon.
- 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_69d381b3e328819094b23b8edcd29b5a |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4e97ed09c8190a3627aa7b5eea62f |
completed | April 7, 2026, 11:24 a.m. |
| PD | Predicate disambiguation | batch_69d4dface5508190a7b42f01ad0a19a2 |
completed | April 7, 2026, 10:42 a.m. |
Created at: April 6, 2026, 12:01 p.m.