Triple
T7652445
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Los Nevados volcanic complex |
E173284
|
entity |
| Predicate | hasPeakCharacteristic |
P274
|
FINISHED |
| Object | snow-capped |
—
|
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: snow-capped | Statement: [Los Nevados volcanic complex, hasPeakCharacteristic, snow-capped]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPeakCharacteristic Context triple: [Los Nevados volcanic complex, hasPeakCharacteristic, snow-capped]
-
A.
hasPeak
Indicates that something possesses or contains a highest point, summit, or maximum value.
-
B.
hasPeakAround
Indicates that something exhibits a maximum value, intensity, or prominence in the vicinity of a specified point, range, or condition.
-
C.
hasSecondaryPeak
Indicates that an entity exhibits an additional, smaller peak or maximum beyond its primary peak in its profile or behavior.
-
D.
hasCharacteristic
chosen
Indicates that an entity possesses, exhibits, or is defined by a particular attribute, feature, or quality.
-
E.
hasPeakNamedAfter
Indicates that a mountain or peak bears a name derived from or dedicated to a particular person, place, or entity.
- 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_69c6995473348190a4f41d110d619a18 |
completed | March 27, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69c7061cbc3c8190a917dd7e71214182 |
completed | March 27, 2026, 10:35 p.m. |
| PD | Predicate disambiguation | batch_69c7015dd8fc8190bc5f52a12bd46209 |
completed | March 27, 2026, 10:14 p.m. |
Created at: March 27, 2026, 3:58 p.m.