Triple
T29833119
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Black Buttes |
E757579
|
entity |
| Predicate | hasNotableSubpeak |
P143205
|
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, hasNotableSubpeak, Colfax Peak]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableSubpeak Context triple: [Black Buttes, hasNotableSubpeak, Colfax Peak]
-
A.
notableSubpeak
chosen
Indicates that one peak is a significant or noteworthy subsidiary summit of another, higher or primary peak.
-
B.
hasNotablePeakVisible
Indicates that a notable peak can be seen from the subject location or entity.
-
C.
hasSecondaryPeak
Indicates that an entity exhibits an additional, smaller peak or maximum beyond its primary peak in its profile or behavior.
-
D.
hasPeak
Indicates that something possesses or contains a highest point, summit, or maximum value.
-
E.
hasSubpeakRelation
Indicates that one peak is a subordinate or subsidiary summit of another, higher or primary peak.
- 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_69fff328ddc0819080642334a41fcf95 |
completed | May 10, 2026, 2:53 a.m. |
| PD | Predicate disambiguation | batch_69fff2e0971c819081aa66f4a6a34b28 |
completed | May 10, 2026, 2:52 a.m. |
Created at: April 29, 2026, 5:35 p.m.