Triple
T23975780
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mount Bond |
E604363
|
entity |
| Predicate | hasSummitAbove |
P154100
|
FINISHED |
| Object | treeline (partially open summit area) |
—
|
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: treeline (partially open summit area) | Statement: [Mount Bond, hasSummitAbove, treeline (partially open summit area)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSummitAbove Context triple: [Mount Bond, hasSummitAbove, treeline (partially open summit area)]
-
A.
hasHigherSummit
Indicates that one entity’s summit is higher in elevation than another entity’s summit.
-
B.
hasSummitCoordinates
Indicates that an entity has specific geographic coordinates identifying the location of its summit.
-
C.
hasNeighboringSummit
Indicates that one summit is directly adjacent to or closely situated next to another summit.
-
D.
isSummitOf
Indicates that one entity is the highest point or peak (summit) of another entity, such as a mountain or structure.
-
E.
hasSummitIn
Indicates that an entity (such as a mountain or organization) has its summit or peak located within a specified place or region.
- F. None of above. chosen
Provenance (4 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_69e29543f40c819087700b7a272afb60 |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f1d2ba11708190b8587bd006249ff5 |
completed | April 29, 2026, 9:43 a.m. |
| PD | Predicate disambiguation | batch_69f161578d54819084a8b35496299993 |
completed | April 29, 2026, 1:39 a.m. |
| PDg | Predicate description generation | batch_69f167dca3608190ace9d2eef56b2af6 |
completed | April 29, 2026, 2:07 a.m. |
Created at: April 17, 2026, 9:26 p.m.