Triple
T29833133
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Black Buttes |
E757579
|
entity |
| Predicate | hasSummitsCharacterizedAs |
P170651
|
FINISHED |
| Object | sharp rocky spires |
—
|
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: sharp rocky spires | Statement: [Black Buttes, hasSummitsCharacterizedAs, sharp rocky spires]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSummitsCharacterizedAs Context triple: [Black Buttes, hasSummitsCharacterizedAs, sharp rocky spires]
-
A.
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).
-
B.
hasMultipleSummits
Indicates that an entity (such as a mountain or peak) consists of more than one distinct summit or high point.
-
C.
isSummitOf
Indicates that one entity is the highest point or peak (summit) of another entity, such as a mountain or structure.
-
D.
isNamedSummitOf
Indicates that one entity is the officially designated summit (highest or principal point) of another entity, such as a mountain or geographic feature.
-
E.
hasSharpSummit
chosen
Indicates that an entity possesses a summit or top that is pointed, steep, or sharply defined in shape.
- 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_69f22457c84c8190a6d9f56bc74082a9 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69fde49a084081909d99b1e0258169d5 |
completed | May 8, 2026, 1:26 p.m. |
| PD | Predicate disambiguation | batch_69fde1d04bd881909a46ecbbf18dfe59 |
completed | May 8, 2026, 1:14 p.m. |
Created at: April 29, 2026, 5:35 p.m.