Triple
T25326374
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Plentzia |
E635025
|
entity |
| Predicate | distanceFromBilbao |
P142844
|
FINISHED |
| Object | approximately 25 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 25 km | Statement: [Plentzia, distanceFromBilbao, approximately 25 km]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceFromBilbao Context triple: [Plentzia, distanceFromBilbao, approximately 25 km]
-
A.
distanceToBilbao
chosen
Indicates the measured distance between a given entity’s location and the city of Bilbao.
-
B.
distanceToPamplona
Indicates the spatial distance between a given entity and the location of Pamplona.
-
C.
distanceToZaragoza
Indicates the spatial distance between a given entity or location and the city of Zaragoza.
-
D.
distanceToMadrid
Indicates the physical distance between a given location or entity and the city of Madrid.
-
E.
distanceToSantander
Indicates the measured or calculated distance between a given entity (such as a location or point) and the city of Santander.
- 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_69e75a9908108190a95427a97020632a |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f72921cf2c8190909bb53f78bcc890 |
completed | May 3, 2026, 10:53 a.m. |
| PD | Predicate disambiguation | batch_69f7283d8cec8190b524c144948bc4ec |
completed | May 3, 2026, 10:49 a.m. |
Created at: April 21, 2026, 1:30 p.m.