Triple
T7223657
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | N'Ko script |
E150322
|
entity |
| Predicate | designedForLanguageFamily |
P75697
|
FINISHED |
| Object | Mande 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: Mande languages | Statement: [N'Ko script, designedForLanguageFamily, Mande languages]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designedForLanguageFamily Context triple: [N'Ko script, designedForLanguageFamily, Mande languages]
-
A.
isInLanguageFamily
Indicates that a language belongs to, or is classified within, a particular language family based on shared linguistic ancestry or characteristics.
-
B.
usesLanguageFamily
Indicates that an entity communicates or operates using a language that belongs to a specified language family.
-
C.
languageFamily
Indicates that two or more languages belong to the same genealogical language family or linguistic lineage.
-
D.
languageFamilyOf
Indicates that one entity is the language family to which the other entity (a specific language) belongs.
-
E.
includesMajorLanguageFamily
Indicates that one entity encompasses, contains, or is associated with a major language family as part of its scope or classification.
- F. None of above. chosen
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_69c687effb44819092b95d07d0368c9f |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6e9b54a5c8190a4a289f32853a8fe |
completed | March 27, 2026, 8:33 p.m. |
| PD | Predicate disambiguation | batch_69c6e761b7fc8190857794d78af1b468 |
completed | March 27, 2026, 8:24 p.m. |
| PDg | Predicate description generation | batch_69c6e8b5f6508190af28e06a7959d717 |
completed | March 27, 2026, 8:29 p.m. |
Created at: March 27, 2026, 2:54 p.m.