Triple
T20081908
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ngorongoro Crater |
E500022
|
entity |
| Predicate | hasRimElevation |
P116877
|
FINISHED |
| Object | about 2200 meters above sea level |
—
|
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: about 2200 meters above sea level | Statement: [Ngorongoro Crater, hasRimElevation, about 2200 meters above sea level]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRimElevation Context triple: [Ngorongoro Crater, hasRimElevation, about 2200 meters above sea level]
-
A.
hasRim
Indicates that one entity possesses or is equipped with a rim as a defining part or feature.
-
B.
hasRimDiameter
Indicates that one entity has a rim whose diameter is measured by or corresponds to the value or object represented by the other entity.
-
C.
hasRimCharacteristic
chosen
Indicates that an entity possesses a specific feature, quality, or attribute related to its rim.
-
D.
hasTypicalElevationRelativeTo
Indicates the usual height or altitude of one entity in comparison to a referenced baseline or other entity.
-
E.
hasRoadAlongRim
Indicates that a road runs adjacent to and follows the contour of a rim or edge of a geographic feature.
- 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_69da627770948190997f486f9a2e370f |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e665588a9c8190886b693b13a215a8 |
completed | April 20, 2026, 5:41 p.m. |
| PD | Predicate disambiguation | batch_69e54cf369b88190931532420517dac7 |
completed | April 19, 2026, 9:45 p.m. |
Created at: April 11, 2026, 3:41 p.m.