Triple
T30959746
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Warjawa |
E788776
|
entity |
| Predicate | belongsToLinguisticSubgroup |
P31853
|
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: [Warjawa, belongsToLinguisticSubgroup, West Chadic languages]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: belongsToLinguisticSubgroup Context triple: [Warjawa, belongsToLinguisticSubgroup, West Chadic languages]
-
A.
linguisticSubgroup
chosen
Indicates that one linguistic group forms a subordinate or specialized subset within a larger linguistic group or family.
-
B.
belongsToLinguisticType
Indicates that something is classified as or associated with a particular linguistic type or category.
-
C.
belongsToLinguisticRegion
Indicates that one linguistic entity (such as a language, dialect, or speech variety) is associated with or situated within a particular linguistic region or area.
-
D.
hasLinguisticAffiliation
Indicates a relationship where an entity is associated with or belongs to a particular language or linguistic group.
-
E.
subGroupOf
Indicates that one group is a subset or specialized division of another, larger group.
- 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_69fe5ec9028081909ae3d6fbe2f4cbbc |
completed | May 8, 2026, 10:08 p.m. |
| PD | Predicate disambiguation | batch_69fe5e1d715881909fc516fafc707644 |
completed | May 8, 2026, 10:05 p.m. |
Created at: April 29, 2026, 8:54 p.m.