Triple
T15489249
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mount Ngungun |
E377134
|
entity |
| Predicate | hasSummitSurface |
P54639
|
FINISHED |
| Object | exposed rock |
—
|
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: exposed rock | Statement: [Mount Ngungun, hasSummitSurface, exposed rock]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSummitSurface Context triple: [Mount Ngungun, hasSummitSurface, exposed rock]
-
A.
hasSummitFeature
Indicates that a summit (or peak) possesses a particular characteristic, attribute, or notable feature.
-
B.
hasSummitArea
chosen
Indicates that an entity has a specific area or surface extent associated with its summit or highest point.
-
C.
hasSummit
Indicates that one entity possesses, features, or includes a summit or highest point as part of its structure or characteristics.
-
D.
hasSummitCoordinates
Indicates that an entity has specific geographic coordinates identifying the location of its summit.
-
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.
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_69d85cd21dcc81908646251b1c26ea00 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e03faaca588190b0397bc2e27a522a |
completed | April 16, 2026, 1:47 a.m. |
| PD | Predicate disambiguation | batch_69ded2874b788190999158e0f043be21 |
completed | April 14, 2026, 11:49 p.m. |
Created at: April 10, 2026, 3:48 a.m.