Triple
T25038930
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Muskiz |
E627054
|
entity |
| Predicate | distanceToBilbao_km |
P142844
|
FINISHED |
| Object | approximately 25 |
—
|
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 | Statement: [Muskiz, distanceToBilbao_km, approximately 25]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToBilbao_km Context triple: [Muskiz, distanceToBilbao_km, approximately 25]
-
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.
distanceToBarcelonaKm
Indicates the physical distance, measured in kilometers, between a given entity’s location and the city of Barcelona.
-
D.
distanceToMadrid
Indicates the physical distance between a given location or entity and the city of Madrid.
-
E.
distanceToZaragoza
Indicates the spatial distance between a given entity or location and the city of Zaragoza.
- 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_69e2ff2a2c088190be513727ee8bfe78 |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f68805b4848190b75da14996d52a38 |
completed | May 2, 2026, 11:25 p.m. |
| PD | Predicate disambiguation | batch_69f68609c0b08190a8e1238a4d97c270 |
completed | May 2, 2026, 11:17 p.m. |
Created at: April 18, 2026, 6:08 a.m.