Triple
T30785104
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chaga |
E783934
|
entity |
| Predicate | isSpokenOnSlopesOf |
P153671
|
FINISHED |
| Object | Mount Kilimanjaro |
—
|
NE NERFINISHED |
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 Kilimanjaro | Statement: [Chaga, isSpokenOnSlopesOf, Mount Kilimanjaro]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isSpokenOnSlopesOf Context triple: [Chaga, isSpokenOnSlopesOf, Mount Kilimanjaro]
-
A.
isSpokenInTerrain
chosen
Indicates that a particular language or speech form is used or occurs within a specific type of terrain or geographical environment.
-
B.
hasSettlementOnSlopes
Indicates that a settlement is located on or extends across the slopes of a landform such as a hill or mountain.
-
C.
isSpokenOn
Indicates that a particular language, phrase, or utterance is used or occurs during a specified time, event, or occasion.
-
D.
isSpokenAlongRiver
Indicates that a language or dialect is used or spoken by communities located along a particular river or river system.
-
E.
isSpokenAlong
Indicates that something (typically a language or dialect) is used or spoken in the regions or areas that follow a particular path, boundary, or route.
- 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_69f224b213c8819083886073f90b647e |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f68fe8168c8190b083be0e33988b9c |
completed | May 2, 2026, 11:59 p.m. |
| PD | Predicate disambiguation | batch_69f68b7b03488190b1db5fde4c7dd6e5 |
completed | May 2, 2026, 11:40 p.m. |
Created at: April 29, 2026, 8:41 p.m.