Triple
T29116110
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mount Elgon National Park (Kenya) |
E737048
|
entity |
| Predicate | highestPointFeature |
P179927
|
FINISHED |
| Object | Mount Elgon 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: Mount Elgon summit area | Statement: [Mount Elgon National Park (Kenya), highestPointFeature, Mount Elgon summit area]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: highestPointFeature Context triple: [Mount Elgon National Park (Kenya), highestPointFeature, Mount Elgon summit area]
-
A.
highestPoint
Indicates that one entity is the point with the greatest elevation or height relative to another entity or defined area.
-
B.
hasHighestPointType
Indicates that the highest point of an entity is of a specified type or category.
-
C.
highPointLocatedOn
Indicates that the highest point of one entity is situated on or atop another entity.
-
D.
containsHighestPointOf
Indicates that one entity includes within its boundaries the location of the highest point of another entity.
-
E.
highestPointRegion
Indicates that one location is the highest point within a specified 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_69f077ed54e08190bb02a744e8121a66 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f72921cf2c8190909bb53f78bcc890 |
completed | May 3, 2026, 10:53 a.m. |
| PD | Predicate disambiguation | batch_69f7283d8cec8190b524c144948bc4ec |
completed | May 3, 2026, 10:49 a.m. |
| PDg | Predicate description generation | batch_69f72920c6208190aa4aba6cb6193109 |
completed | May 3, 2026, 10:53 a.m. |
Created at: April 28, 2026, 11:22 a.m.