Triple
T29833122
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Black Buttes |
E757579
|
entity |
| Predicate | hasHighestSubpeak |
P193076
|
FINISHED |
| Object | Colfax Peak |
—
|
NE NERFINISHED |
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: Colfax Peak | Statement: [Black Buttes, hasHighestSubpeak, Colfax Peak]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHighestSubpeak Context triple: [Black Buttes, hasHighestSubpeak, Colfax Peak]
-
A.
highestSubpeakOf
chosen
Indicates that one peak is the tallest subordinate peak directly associated with a higher main peak.
-
B.
hasPeak
Indicates that something possesses or contains a highest point, summit, or maximum value.
-
C.
hasHighest
Indicates that one entity possesses the greatest value, rank, or level in a specified attribute or set compared to all others.
-
D.
hasPeakOver
Indicates that one entity’s peak (such as a maximum value, height, or intensity) exceeds that of another entity.
-
E.
hasSharperPeakThan
Indicates that one entity’s peak (e.g., in a graph, distribution, or signal) is more pointed or narrow than the peak of another 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_69f22457c84c8190a6d9f56bc74082a9 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69fd76d1e5208190a6f26651492d1e3c |
completed | May 8, 2026, 5:38 a.m. |
| PD | Predicate disambiguation | batch_69fd702a226c81908edfda00f4be4130 |
completed | May 8, 2026, 5:10 a.m. |
Created at: April 29, 2026, 5:35 p.m.