Triple
T29355386
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kuvi people |
E744425
|
entity |
| Predicate | associatedLanguageISO |
P20184
|
FINISHED |
| Object | kfb |
—
|
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: kfb | Statement: [Kuvi people, associatedLanguageISO, kfb]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedLanguageISO Context triple: [Kuvi people, associatedLanguageISO, kfb]
-
A.
associatedLanguageScript
Indicates that there is a relationship between a language and the script or writing system used to represent it.
-
B.
closelyAssociatedLanguage
Indicates that one language is closely connected to another, such as through frequent co-use, mutual influence, or strong cultural or regional association.
-
C.
isWorkingLanguageOf
Indicates that a particular language is officially used as a medium of work, communication, or operation within a specified organization, institution, or context.
-
D.
languageAssociation
chosen
Indicates an association or relationship between entities based on a language they use, represent, or are linked to.
-
E.
languageUsedAs
Indicates that one language is employed in a specific role, function, or context relative to another entity or situation.
- 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_69f0a79aee588190b490f19d93c6e52d |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_6a035b78140081908e451cb63d3c1c7c |
completed | May 12, 2026, 4:55 p.m. |
| PD | Predicate disambiguation | batch_6a035af3d8f48190bf1f3741d374404e |
completed | May 12, 2026, 4:53 p.m. |
Created at: April 28, 2026, 2:11 p.m.