Triple
T31560950
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sarria |
E805259
|
entity |
| Predicate | minimumDistanceForCompostelaStartingHere |
P94234
|
FINISHED |
| Object | more than 100 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: more than 100 km | Statement: [Sarria, minimumDistanceForCompostelaStartingHere, more than 100 km]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: minimumDistanceForCompostelaStartingHere Context triple: [Sarria, minimumDistanceForCompostelaStartingHere, more than 100 km]
-
A.
hasMinimumDistanceForCompostela
chosen
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.
distanceToSantander
Indicates the measured or calculated distance between a given entity (such as a location or point) and the city of Santander.
-
E.
distanceToBilbao
Indicates the measured distance between a given entity’s location and the city of Bilbao.
- 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_69f6d74b20a48190900dda1014cc13a8 |
completed | May 3, 2026, 5:04 a.m. |
| PD | Predicate disambiguation | batch_69f6d26f27dc8190ae426a3e1573933e |
completed | May 3, 2026, 4:43 a.m. |
Created at: April 30, 2026, 10:15 p.m.