Triple
T11303166
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lobi language |
E267645
|
entity |
| Predicate | subclassification |
P24573
|
FINISHED |
| Object | Southern Gur languages |
—
|
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: Southern Gur languages | Statement: [Lobi language, subclassification, Southern Gur languages]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: subclassification Context triple: [Lobi language, subclassification, Southern Gur languages]
-
A.
subclassificationStatus
Indicates the classification state or category assigned to a subclass within a broader classification system.
-
B.
secondaryClassification
Indicates a secondary or additional categorization assigned to an entity beyond its primary classification.
-
C.
categorySubdivision
Indicates that one category functions as a subdivision or subcategory within another broader category.
-
D.
subfamily
Indicates that one taxonomic group is a subfamily within a larger family, representing an intermediate rank in biological classification.
-
E.
isClassifiedUnder
chosen
Indicates that one entity is categorized or grouped within a broader class, type, or category represented by another entity.
- 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_69d6aac993a08190a6f36445ebaf9a43 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e9a5c3788190ba54eda514b97903 |
completed | April 9, 2026, 6:02 p.m. |
| PD | Predicate disambiguation | batch_69d787aa31888190860eecaa80da5b20 |
completed | April 9, 2026, 11:04 a.m. |
Created at: April 8, 2026, 9:32 p.m.