Triple
T8144887
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Monistrol-sur-Loire |
E190182
|
entity |
| Predicate | distanceToLePuy-en-Velay |
P80947
|
FINISHED |
| Object | approximately 50 km northeast |
—
|
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 50 km northeast | Statement: [Monistrol-sur-Loire, distanceToLePuy-en-Velay, approximately 50 km northeast]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToLePuy-en-Velay Context triple: [Monistrol-sur-Loire, distanceToLePuy-en-Velay, approximately 50 km northeast]
-
A.
distanceToPontDuGard
Indicates the measured spatial distance between a given entity and the Pont du Gard.
-
B.
distanceFromLyon
Indicates the spatial distance between a given entity and the city of Lyon.
-
C.
distanceFromFoixKilometres
Indicates the physical distance, measured in kilometers, between a given place or entity and the location of Foix.
-
D.
distanceToPyrenees
Indicates the spatial distance between a given location or entity and the Pyrenees.
-
E.
distanceToPerpignan
Indicates the physical distance between a given place or entity and the city of Perpignan.
- 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_69ca82be7ba8819087de0147e9292c83 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb4445f1948190b8d319b60dd47f65 |
completed | March 31, 2026, 3:49 a.m. |
| PD | Predicate disambiguation | batch_69cb369c0d0481908762c488d7f77e74 |
completed | March 31, 2026, 2:51 a.m. |
| PDg | Predicate description generation | batch_69cb39d20e78819092ea9e04357be008 |
completed | March 31, 2026, 3:04 a.m. |
Created at: March 30, 2026, 5:36 p.m.