Triple
T35538337
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Risco de los Claveles |
E1026992
|
entity |
| Predicate | closestHigherNeighbor |
P126574
|
FINISHED |
| Object | Peñalara |
—
|
NE NERFINISHED |
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: Peñalara | Statement: [Risco de los Claveles, closestHigherNeighbor, Peñalara]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: closestHigherNeighbor Context triple: [Risco de los Claveles, closestHigherNeighbor, Peñalara]
-
A.
nearestMajorNeighbor
Indicates that one entity is the closest significant or major neighboring entity to another in terms of spatial proximity.
-
B.
highestNearbyPoint
Indicates that one location is the highest point within a specified surrounding area relative to another location.
-
C.
nearestHigherPeak
chosen
Indicates that one peak is the closest peak that has a higher elevation than another specified peak.
-
D.
closestTo
Indicates that one entity is nearer in distance to a reference entity than any other comparable entity.
-
E.
nearestPass
Indicates that one entity is the closest in distance or proximity to another entity compared to all other possible entities or paths.
- 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_69f76dff7e508190b28ceeee770dce23 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fcc4b700748190ae00b21d09c96695 |
completed | May 7, 2026, 4:58 p.m. |
| PD | Predicate disambiguation | batch_69fcb0f9d3d881908a049475182fb039 |
completed | May 7, 2026, 3:34 p.m. |
Created at: May 3, 2026, 4:04 p.m.