Triple
T33986104
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tulle |
E871412
|
entity |
| Predicate | distanceToClermont-Ferrand |
P78330
|
FINISHED |
| Object | about 150 km |
—
|
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: about 150 km | Statement: [Tulle, distanceToClermont-Ferrand, about 150 km]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToClermont-Ferrand Context triple: [Tulle, distanceToClermont-Ferrand, about 150 km]
-
A.
distanceToClermontFerrand_km
chosen
Indicates the physical distance, measured in kilometers, between a given place and Clermont-Ferrand.
-
B.
distanceToSaint-Étienne
Indicates the measured or specified distance between a given entity and the location Saint-Étienne.
-
C.
distanceToChambéryKilometersApprox
Indicates an approximate distance, measured in kilometers, between a given entity and the location of Chambéry.
-
D.
distanceFromLyon
Indicates the spatial distance between a given entity and the city of Lyon.
-
E.
distanceFromToulouse
Indicates the measured spatial distance between a given entity and the location of Toulouse.
- 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_69f3499e964c8190b674b03f6f791b4b |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a037c8ae0248190b7e2ce4bf852c22d |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379f963908190846d232f386fd98f |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:50 a.m.