Triple
T1187745
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bantu languages |
E25285
|
entity |
| Predicate | classificationScheme |
P6736
|
FINISHED |
| Object | Guthrie classification |
—
|
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: Guthrie classification | Statement: [Bantu languages, classificationScheme, Guthrie classification]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: classificationScheme Context triple: [Bantu languages, classificationScheme, Guthrie classification]
-
A.
classificationSystem
chosen
Indicates a relationship where an entity is organized or categorized according to a particular classification scheme or taxonomy.
-
B.
classificationSystemName
Indicates the name or label assigned to a particular classification system used to categorize or organize entities.
-
C.
classificationStart
Indicates the point in time or process at which a classification or categorization of an entity begins.
-
D.
classificationApproach
Indicates the method or strategy used to categorize or assign entities into classes or groups.
-
E.
classificationLevel
Indicates the degree or tier within an ordered system or hierarchy to which something is assigned for categorization or control purposes.
- 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_69a49427d98881908646d6c63b8cea1e |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4bd568cf481908d10cf19a3ce28f3 |
completed | March 1, 2026, 10:27 p.m. |
| PD | Predicate disambiguation | batch_69a4bb5bacc481909e8dfd5215e4711a |
completed | March 1, 2026, 10:19 p.m. |
Created at: March 1, 2026, 7:45 p.m.