Triple
T34522891
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pucará de Tilcara |
E886323
|
entity |
| Predicate | distanceFromTilcaraCenter |
P205453
|
FINISHED |
| Object | approximately 1 kilometer |
—
|
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 1 kilometer | Statement: [Pucará de Tilcara, distanceFromTilcaraCenter, approximately 1 kilometer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceFromTilcaraCenter Context triple: [Pucará de Tilcara, distanceFromTilcaraCenter, approximately 1 kilometer]
-
A.
distanceToTalca_km
Indicates the physical distance, measured in kilometers, between a given entity and the city of Talca.
-
B.
distanceToTrelew
Indicates the spatial distance between a given entity and the location Trelew.
-
C.
distanceFromLaPazApproximate
Indicates an approximate measure of how far something is from La Paz, typically expressed as a rough distance rather than an exact value.
-
D.
distanceToChilecito
Indicates the spatial distance between a given entity and the location of Chilecito.
-
E.
distanceFromCusco
Indicates the measured spatial distance between a given location or entity and the city of Cusco.
- 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_69f349cd7c148190aa99192b126d1527 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a037c92f03c8190ae2751270b195423 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379fbe4a08190bfe65ebd141164e9 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c80ba448190853011097a151b7e |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 1, 2026, 2:02 a.m.