Triple
T27494494
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Libertador General San Martín |
E693985
|
entity |
| Predicate | distanceToSanSalvadorDeJujuy |
P200142
|
FINISHED |
| Object | approximately 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: approximately 100 km | Statement: [Libertador General San Martín, distanceToSanSalvadorDeJujuy, approximately 100 km]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToSanSalvadorDeJujuy Context triple: [Libertador General San Martín, distanceToSanSalvadorDeJujuy, approximately 100 km]
-
A.
distanceFromSaltaByRoad_km
Indicates the distance in kilometers between an entity and Salta when traveling by road.
-
B.
distanceToBahíaBlanca
Indicates the measured distance between a given entity and the location of Bahía Blanca.
-
C.
distanceToNeuquénCity
Indicates the spatial distance between a given location and the city of Neuquén.
-
D.
distanceToNeuquénCity_km
Indicates the physical distance, measured in kilometers, between an entity and the city of Neuquén.
-
E.
distanceFromCafayateByRoad_km
Indicates the distance in kilometers from Cafayate to another location when traveling by road.
- 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_69ef5382b9648190be0b1ef2ad5d043c |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69ff779e3f0c8190a861f1e4000fd9d9 |
completed | May 9, 2026, 6:06 p.m. |
| PD | Predicate disambiguation | batch_69ff77202638819086e4b9f9c0bc7b31 |
completed | May 9, 2026, 6:04 p.m. |
| PDg | Predicate description generation | batch_69ff779d3d788190af5a2dbc4d7ca3c8 |
completed | May 9, 2026, 6:06 p.m. |
Created at: April 27, 2026, 1:07 p.m.