Triple
T26669705
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ojos del Caburgua |
E672290
|
entity |
| Predicate | approxDistanceFromCaburguaLake |
P180484
|
FINISHED |
| Object | a few kilometers |
—
|
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: a few kilometers | Statement: [Ojos del Caburgua, approxDistanceFromCaburguaLake, a few kilometers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approxDistanceFromCaburguaLake Context triple: [Ojos del Caburgua, approxDistanceFromCaburguaLake, a few kilometers]
-
A.
hasApproximateRoundTripDistanceFromMaroonLake
Indicates that an entity has an approximate total round-trip distance measured from Maroon Lake.
-
B.
approxDistanceFromPucón
Indicates an approximate spatial distance measured from the location of Pucón to another place or entity.
-
C.
distanceFromSabieApprox
Indicates an approximate measure of how far something is from Sabie.
-
D.
distanceToBadwaterBasin
Indicates the measured spatial distance between a given entity and Badwater Basin.
-
E.
approxDistanceFromEnsenada
Indicates that one entity is located at an approximate distance from the reference location Ensenada.
- 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_69eecda00a9c8190b2691f4d89db03b6 |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69f7431c0eec81909ead443e07d75e18 |
completed | May 3, 2026, 12:44 p.m. |
| PD | Predicate disambiguation | batch_69f74143cf708190a12d487884298437 |
completed | May 3, 2026, 12:36 p.m. |
| PDg | Predicate description generation | batch_69f7431aac148190bb6aac59817c174a |
completed | May 3, 2026, 12:44 p.m. |
Created at: April 27, 2026, 3:12 a.m.