Triple
T31560924
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sarria |
E805259
|
entity |
| Predicate | distanceToSantiagoDeCompostelaByCamino |
P19519
|
FINISHED |
| Object | approximately 111 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: approximately 111 km | Statement: [Sarria, distanceToSantiagoDeCompostelaByCamino, approximately 111 km]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToSantiagoDeCompostelaByCamino Context triple: [Sarria, distanceToSantiagoDeCompostelaByCamino, approximately 111 km]
-
A.
hasMinimumDistanceForCompostela
Indicates that there is a required minimum travel distance that must be met in order to qualify for receiving the Compostela.
-
B.
distanceToPamplona
Indicates the spatial distance between a given entity and the location of Pamplona.
-
C.
distanceToSalamanca
Indicates the spatial distance between a given entity and the location of Salamanca.
-
D.
distanceToSantiago_km
chosen
Indicates the physical distance, measured in kilometers, between a given location and Santiago.
-
E.
pilgrimageDistance
Indicates the distance that must be traveled to complete a specified pilgrimage route or journey.
- 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_69f348d22e088190ad555d5bd42f9da0 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_6a01d9ca07b88190b4ad70b6336447b6 |
completed | May 11, 2026, 1:29 p.m. |
| PD | Predicate disambiguation | batch_6a01d807c3048190b79f0b6b933dd3b7 |
completed | May 11, 2026, 1:22 p.m. |
Created at: April 30, 2026, 10:15 p.m.