Triple
T3142131
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mount Pico |
E65673
|
entity |
| Predicate | hasSummitClimate |
P8666
|
FINISHED |
| Object | alpine climate |
—
|
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: alpine climate | Statement: [Mount Pico, hasSummitClimate, alpine climate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSummitClimate Context triple: [Mount Pico, hasSummitClimate, alpine climate]
-
A.
hasSummitFeature
chosen
Indicates that a summit (or peak) possesses a particular characteristic, attribute, or notable feature.
-
B.
hasSummitFacility
Indicates that one entity possesses or provides a facility or infrastructure located at the summit of another entity (such as a mountain, hill, or peak).
-
C.
hasSummit
Indicates that one entity possesses, features, or includes a summit or highest point as part of its structure or characteristics.
-
D.
hasSummitConditions
Indicates that specific environmental or situational conditions required for a summit (e.g., peak ascent or high-level meeting) are present or satisfied.
-
E.
hasSummitBorder
Indicates that two or more entities share a common boundary that runs along a summit or ridgeline.
- 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_69ad8582f564819088c27e1f96153938 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada579b07c8190a7b316f499911a2d |
completed | March 8, 2026, 4:36 p.m. |
| PD | Predicate disambiguation | batch_69ad9df840088190a26a1516f4c1f056 |
completed | March 8, 2026, 4:04 p.m. |
Created at: March 8, 2026, 3:05 p.m.