Triple
T38613639
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Togo Kan |
E934548
|
entity |
| Predicate | isSpokenInVillageCluster |
P109887
|
FINISHED |
| Object | Dogon villages |
—
|
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: Dogon villages | Statement: [Togo Kan, isSpokenInVillageCluster, Dogon villages]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isSpokenInVillageCluster Context triple: [Togo Kan, isSpokenInVillageCluster, Dogon villages]
-
A.
isSpokenInTerrain
Indicates that a particular language or speech form is used or occurs within a specific type of terrain or geographical environment.
-
B.
isSpokenAround
Indicates that something (such as a language, phrase, or expression) is commonly spoken in the vicinity of, or within the general area surrounding, a particular place or entity.
-
C.
hasVillageCluster
Indicates that one entity contains, is associated with, or is organized into a specific cluster or grouping of villages.
-
D.
spokenInLocality
chosen
Indicates that a language, dialect, or speech form is used or spoken within a specific locality or geographic area.
-
E.
isVillage
Indicates that the subject entity is classified as a village, typically a small human settlement or community.
- 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_69f76eccd6d081909ccce171011739a1 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcdfbc71c481908ba7f87907b17782 |
completed | May 7, 2026, 6:53 p.m. |
| PD | Predicate disambiguation | batch_69fcdbe580b8819087f143596b2c79c0 |
completed | May 7, 2026, 6:37 p.m. |
Created at: May 3, 2026, 4:32 p.m.