Triple
T22951360
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Botatwe languages |
E570026
|
entity |
| Predicate | hasMemberLanguage |
P7390
|
FINISHED |
| Object | Lenje language |
—
|
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: Lenje language | Statement: [Botatwe languages, hasMemberLanguage, Lenje language]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Lenje language Context triple: [Botatwe languages, hasMemberLanguage, Lenje language]
-
A.
Lenje language
chosen
The Lenje language is a Bantu language spoken primarily by the Lenje people of central Zambia, closely related to the Tonga language of the same region.
-
B.
Lauje language
The Lauje language is an Austronesian language spoken by the Lauje people of Central Sulawesi, Indonesia.
-
C.
Taje language
The Taje language is an Austronesian language of the Kaili–Pamona group spoken by a small community in Central Sulawesi, Indonesia.
-
D.
Lehali language
The Lehali language is an Oceanic language spoken by a small community on the Banks Islands in northern Vanuatu.
-
E.
Lasgerdi language
The Lasgerdi language is an Iranian language spoken in parts of north-central Iran and classified within the Semnani branch of Northwestern Iranian languages.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e2459199d08190a8184ee2aa935842 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f181a285448190a718734fe933d51a |
completed | April 29, 2026, 3:57 a.m. |
Created at: April 17, 2026, 3:46 p.m.