Triple
T11010669
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | El Panecillo |
E260237
|
entity |
| Predicate | elevationRelativeToQuito |
P96991
|
FINISHED |
| Object | about 200 meters above central Quito |
—
|
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: about 200 meters above central Quito | Statement: [El Panecillo, elevationRelativeToQuito, about 200 meters above central Quito]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: elevationRelativeToQuito Context triple: [El Panecillo, elevationRelativeToQuito, about 200 meters above central Quito]
-
A.
distanceFromQuito
Indicates the spatial distance between a given entity or location and the city of Quito.
-
B.
distanceFromBogotá
Indicates the spatial distance separating a given entity or location from the city of Bogotá.
-
C.
distanceToGuayaquil_km
Indicates the physical distance, measured in kilometers, between an entity’s location and the city of Guayaquil.
-
D.
elevationApproxMeters
Indicates the approximate elevation of an entity above sea level, measured in meters.
-
E.
distanceFromLaPazApproximate
Indicates an approximate measure of how far something is from La Paz, typically expressed as a rough distance rather than an exact value.
- 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_69d6aa9687448190b28d353b1b6a610e |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d797899a388190aa8fe813eac4dba7 |
completed | April 9, 2026, 12:11 p.m. |
| PD | Predicate disambiguation | batch_69d72e96be6c8190a46c69f61b2d8cd4 |
completed | April 9, 2026, 4:44 a.m. |
| PDg | Predicate description generation | batch_69d733b27ffc81908ab1b8df198cd5c7 |
completed | April 9, 2026, 5:05 a.m. |
Created at: April 8, 2026, 9:25 p.m.