Triple
T11085246
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pico Norte |
E262102
|
entity |
| Predicate | hasRelativePositionOnCerroDeLaSilla |
P97137
|
FINISHED |
| Object | northern summit |
—
|
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: northern summit | Statement: [Pico Norte, hasRelativePositionOnCerroDeLaSilla, northern summit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRelativePositionOnCerroDeLaSilla Context triple: [Pico Norte, hasRelativePositionOnCerroDeLaSilla, northern summit]
-
A.
hasSummitOnSideOf
Indicates that the summit or highest point of one geographic feature is located on the side of another feature.
-
B.
isOnHill
Indicates that one entity is located on or atop a hill relative to another reference frame or context.
-
C.
hasNearbyPromontory
Indicates that one geographic feature or location is situated close to a promontory or headland.
-
D.
hasHighestPointNear
Indicates that one entity’s highest point is located close to another specified entity or location.
-
E.
locatedOnEasternSlopeOf
Indicates that one entity is situated on the eastern slope or side of another geographic feature or elevation.
- 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_69d6aa9983c08190b0ef61603b69feac |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d799c2c7d4819087ac793153340178 |
completed | April 9, 2026, 12:21 p.m. |
| PD | Predicate disambiguation | batch_69d744185a5881909ba4cf151d1798ec |
completed | April 9, 2026, 6:15 a.m. |
| PDg | Predicate description generation | batch_69d750ca52ec8190a559432a5de106fd |
completed | April 9, 2026, 7:10 a.m. |
Created at: April 8, 2026, 9:27 p.m.