Triple
T36873983
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North summit of Llaima |
E911294
|
entity |
| Predicate | hasSummitCountOfParent |
P64502
|
FINISHED |
| Object | one of two main summits of Llaima |
—
|
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: one of two main summits of Llaima | Statement: [North summit of Llaima, hasSummitCountOfParent, one of two main summits of Llaima]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSummitCountOfParent Context triple: [North summit of Llaima, hasSummitCountOfParent, one of two main summits of Llaima]
-
A.
hasSummitCountApprox
Indicates that an entity is associated with an approximate number of summits or peak ascents.
-
B.
hasSummitAbove
Indicates that one summit is located at a higher elevation than another summit.
-
C.
hasSummitSubfeature
Indicates that one geographic or structural feature includes another feature specifically located at or forming its summit.
-
D.
hasNeighboringSummit
Indicates that one summit is directly adjacent to or closely situated next to another summit.
-
E.
summitCount
chosen
Indicates the number of summits or peak ascents associated with an 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_69f76e82339881909607a65c0503d941 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a002ae74da08190a4b47e0ff0f7f8fe |
completed | May 10, 2026, 6:51 a.m. |
| PD | Predicate disambiguation | batch_6a0029cc369c81909578e52c4a75ab18 |
completed | May 10, 2026, 6:46 a.m. |
Created at: May 3, 2026, 4:13 p.m.