Triple
T30960400
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pankshin area |
E788795
|
entity |
| Predicate | linguisticFamilyOfMainLanguage |
P35117
|
FINISHED |
| Object | West Chadic languages |
—
|
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: West Chadic languages | Statement: [Pankshin area, linguisticFamilyOfMainLanguage, West Chadic languages]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: linguisticFamilyOfMainLanguage Context triple: [Pankshin area, linguisticFamilyOfMainLanguage, West Chadic languages]
-
A.
languageFamilyOfMajorLanguage
Indicates that one entity is the language family to which the other, a major language, belongs.
-
B.
languageFamily
Indicates that two or more languages belong to the same genealogical language family or linguistic lineage.
-
C.
majorLanguageFamilies
Indicates that one entity is a primary or dominant language family to which the other entity (a language or group of languages) belongs.
-
D.
languageFamilyOf
chosen
Indicates that one entity is the language family to which the other entity (a specific language) belongs.
-
E.
languageOfFamily
Indicates the language or languages commonly used or associated with a particular family.
- 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_69f224c28c1881908c33b45d689f1724 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6953bafb88190a860e9c68a3dd4b2 |
completed | May 3, 2026, 12:22 a.m. |
| PD | Predicate disambiguation | batch_69f690ef92308190903a54fc74233269 |
completed | May 3, 2026, 12:03 a.m. |
Created at: April 29, 2026, 8:54 p.m.