Triple
T11315819
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pico Sur |
E267961
|
entity |
| Predicate | positionOnCerroDeLaSilla |
P97137
|
FINISHED |
| Object | southern peak |
—
|
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: southern peak | Statement: [Pico Sur, positionOnCerroDeLaSilla, southern peak]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionOnCerroDeLaSilla Context triple: [Pico Sur, positionOnCerroDeLaSilla, southern peak]
-
A.
hasRelativePositionOnCerroDeLaSilla
chosen
Indicates that one entity has a specific spatial or locational relationship relative to Cerro de la Silla.
-
B.
locatedOnEasternSlopeOf
Indicates that one entity is situated on the eastern slope or side of another geographic feature or elevation.
-
C.
NazcaLinesLocation
Indicates that a location is the site where the Nazca Lines are found or situated.
-
D.
positionRelativeToSummit
Indicates the spatial relationship of an entity’s location with respect to the summit of a feature or structure.
-
E.
positionInColombia
Indicates that one entity occupies or is located at a specific position within the geographic boundaries of Colombia.
- 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_69d6aaca5c24819083db46a30d86cb34 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e9c2c7b081909af8acebc8aa93aa |
completed | April 9, 2026, 6:02 p.m. |
| PD | Predicate disambiguation | batch_69d787ad575081908274280bf75d95fd |
completed | April 9, 2026, 11:04 a.m. |
Created at: April 8, 2026, 9:32 p.m.