Triple
T24064338
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North Bantoid |
E596045
|
entity |
| Predicate | isLinguisticBranchOf |
P24621
|
FINISHED |
| Object | Bantoid |
—
|
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: Bantoid | Statement: [North Bantoid, isLinguisticBranchOf, Bantoid]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isLinguisticBranchOf Context triple: [North Bantoid, isLinguisticBranchOf, Bantoid]
-
A.
languageFamilyBranchOf
chosen
Indicates that one language family branch is a sub-group or subdivision within a larger language family.
-
B.
inLanguageFamily
Indicates that two languages belong to the same linguistic family or classification.
-
C.
sharesLinguisticFamilyWith
Indicates that two languages belong to the same linguistic family or branch within a language family.
-
D.
linguisticallyRelatedTo
Indicates that two entities are connected through a linguistic relationship, such as sharing a common language, origin, structure, or other language-based association.
-
E.
derivedFromLanguageFamily
Indicates that one language originates from, or historically descends from, 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_69e288c25c008190850cf447940ab181 |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1da598dec8190a625309fd8f10f1d |
completed | April 29, 2026, 10:15 a.m. |
| PD | Predicate disambiguation | batch_69f1764b1d4c8190b12590c6339c31c1 |
completed | April 29, 2026, 3:08 a.m. |
Created at: April 17, 2026, 10:39 p.m.