Triple
T37616904
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Olusoga |
E935947
|
entity |
| Predicate | languageSubGroup |
P31853
|
FINISHED |
| Object | Southern Bantoid languages |
E26698
|
NE 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: Southern Bantoid languages | Statement: [Olusoga, languageSubGroup, Southern Bantoid languages]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languageSubGroup Context triple: [Olusoga, languageSubGroup, Southern Bantoid languages]
-
A.
linguisticSubgroup
chosen
Indicates that one linguistic group forms a subordinate or specialized subset within a larger linguistic group or family.
-
B.
regionalLanguageGroup
Indicates that the related entities belong to the same group defined by shared or similar regional languages.
-
C.
languageGroupType
Indicates the classification relationship that specifies what type or category a particular language group belongs to.
-
D.
usesLanguageSubfamily
Indicates that one entity communicates or operates using a language that belongs to a specified language subfamily.
-
E.
languageGroupName
Indicates the name assigned to a particular language group or linguistic classification.
- F. None of above.
Provenance (4 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_69f76ed16b748190ad6add183b1be688 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a01a48fbbd481908ccf75551dcf4647 |
completed | May 11, 2026, 9:42 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a40afe8ecf08190b89798e6d290a6b3 |
completed | June 28, 2026, 5:23 a.m. |
| PD | Predicate disambiguation | batch_6a01a2d6db208190b11c1af601a544f5 |
completed | May 11, 2026, 9:35 a.m. |
Created at: May 3, 2026, 4:18 p.m.