Triple
T3696380
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mawenzi |
E78468
|
entity |
| Predicate | relativePositionOnKilimanjaro |
P44470
|
FINISHED |
| Object | east of Kibo |
—
|
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: east of Kibo | Statement: [Mawenzi, relativePositionOnKilimanjaro, east of Kibo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relativePositionOnKilimanjaro Context triple: [Mawenzi, relativePositionOnKilimanjaro, east of Kibo]
-
A.
relativeToMountEverest
Indicates a relationship that compares or situates something in reference to Mount Everest, such as in terms of location, height, scale, or significance.
-
B.
positionRelativeToSummit
chosen
Indicates the spatial relationship of an entity’s location with respect to the summit of a feature or structure.
-
C.
nearestSummit
Indicates that one summit is the closest in distance to a given reference point or location compared to all other summits.
-
D.
includesHighestMountainOnEarth
Indicates that the subject entity contains or encompasses the location of the tallest mountain on Earth.
-
E.
reachesSummit
Indicates that an entity successfully arrives at or attains the highest point or summit of something.
- 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_69ad85e3b1888190abc983e06968696d |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc50f9ad88190a926042fa73d65dc |
completed | March 8, 2026, 6:50 p.m. |
| PD | Predicate disambiguation | batch_69adb84dc5808190850aa6975cb09e27 |
completed | March 8, 2026, 5:56 p.m. |
Created at: March 8, 2026, 3:26 p.m.