Triple
T1393439
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nevado San Francisco |
E30611
|
entity |
| Predicate | hasSummitConditions |
P27685
|
FINISHED |
| Object | low oxygen levels |
—
|
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: low oxygen levels | Statement: [Nevado San Francisco, hasSummitConditions, low oxygen levels]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSummitConditions Context triple: [Nevado San Francisco, hasSummitConditions, low oxygen levels]
-
A.
hasSummit
Indicates that one entity possesses, features, or includes a summit or highest point as part of its structure or characteristics.
-
B.
hasSummitFeature
Indicates that a summit (or peak) possesses a particular characteristic, attribute, or notable feature.
-
C.
hasSummitCoordinates
Indicates that an entity has specific geographic coordinates identifying the location of its summit.
-
D.
hasSummitName
Indicates that a summit or peak is identified by a specific name.
-
E.
reachesSummit
Indicates that an entity successfully arrives at or attains the highest point or summit of something.
- 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_69a498fd4e408190bd73eca30ea9754c |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c37cd99081908d16014e0b99992d |
completed | March 1, 2026, 10:53 p.m. |
| PD | Predicate disambiguation | batch_69a4bf017f8081908572121560ec621f |
completed | March 1, 2026, 10:34 p.m. |
| PDg | Predicate description generation | batch_69a4c13270d8819081d8ee1be34cabf5 |
completed | March 1, 2026, 10:44 p.m. |
Created at: March 1, 2026, 7:59 p.m.