Triple
T38196067
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Breckenridge Peak 6–10 complex |
E1005613
|
entity |
| Predicate | hasSummitGroup |
P8024
|
FINISHED |
| Object | multiple mountain summits |
—
|
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: multiple mountain summits | Statement: [Breckenridge Peak 6–10 complex, hasSummitGroup, multiple mountain summits]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSummitGroup Context triple: [Breckenridge Peak 6–10 complex, hasSummitGroup, multiple mountain summits]
-
A.
hasSummit
chosen
Indicates that one entity possesses, features, or includes a summit or highest point as part of its structure or characteristics.
-
B.
hasSummitIn
Indicates that an entity (such as a mountain or organization) has its summit or peak located within a specified place or region.
-
C.
hasSummitRole
Indicates that an entity holds a specific role or function within a summit or summit-related event.
-
D.
hasSummitAccess
Indicates that an entity is permitted or able to reach or enter the summit or highest level of a specified place, system, or structure.
-
E.
hasSummitRegister
Indicates that a summit or peak possesses an official register or logbook for recording visitors or ascents.
- 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_69f76dbd22f48190940318cea061e8bb |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a007aa8d3a481908543f9b5d562a90c |
completed | May 10, 2026, 12:31 p.m. |
| PD | Predicate disambiguation | batch_6a007a44996481908688ccfdbc56511d |
completed | May 10, 2026, 12:29 p.m. |
Created at: May 3, 2026, 4:29 p.m.