Triple
T25291793
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bantu zone N |
E634105
|
entity |
| Predicate | hasLinguisticFamilyCode |
P6290
|
FINISHED |
| Object | N |
—
|
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: N | Statement: [Bantu zone N, hasLinguisticFamilyCode, N]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLinguisticFamilyCode Context triple: [Bantu zone N, hasLinguisticFamilyCode, N]
-
A.
hasLinguisticCode
Indicates that an entity is associated with a specific linguistic identifier or code (such as a language or script code) that characterizes its linguistic properties.
-
B.
languageFamilyCode
chosen
Indicates the language family to which a given language belongs, represented by a standardized code.
-
C.
isInLanguageFamily
Indicates that a language belongs to, or is classified within, a particular language family based on shared linguistic ancestry or characteristics.
-
D.
hasPrimaryVernacularLanguageFamily
Indicates that an entity’s main vernacular language belongs to a specified language family.
-
E.
languageFamilyAssociated
Indicates that there is an association or connection between a language and a particular language 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_69e75a9503d48190b80a005c6af0cb50 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f65f7731e4819099d5bd3d915ee266 |
completed | May 2, 2026, 8:32 p.m. |
| PD | Predicate disambiguation | batch_69f65c1f94ac8190bc6fbc7916fc0d82 |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 21, 2026, 1:22 p.m.