Triple
T11643129
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Khoe–Kwadi language family |
E276708
|
entity |
| Predicate | hasMemberLanguageStatus |
P25828
|
FINISHED |
| Object | extinct language |
—
|
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: extinct language | Statement: [Khoe–Kwadi language family, hasMemberLanguageStatus, extinct language]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMemberLanguageStatus Context triple: [Khoe–Kwadi language family, hasMemberLanguageStatus, extinct language]
-
A.
hasMemberLanguage
Indicates that one entity is a language that is a constituent or member of a larger language group, family, or collection represented by the other entity.
-
B.
hasLanguageStatus
chosen
Indicates that an entity has a particular status or condition regarding its language use, recognition, or classification.
-
C.
hasOfficerLanguage
Indicates that an officer is able or authorized to communicate in a specified language.
-
D.
hasContactWithLanguage
Indicates that an entity has some form of interaction, exposure, or engagement with a particular language.
-
E.
eligibleLanguage
Indicates that a particular language satisfies the required conditions to be considered valid or allowed in a given context.
- 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_69d6aafbb3c081908a9cdb4ecb8d981d |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a2cb4ca88190a9322f08416d3974 |
completed | April 10, 2026, 7:12 a.m. |
| PD | Predicate disambiguation | batch_69d85dd94bdc819091fa2ed33eb31624 |
completed | April 10, 2026, 2:18 a.m. |
Created at: April 8, 2026, 9:39 p.m.