Triple
T38077865
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kho |
E950768
|
entity |
| Predicate | languageStatusInChitral |
P176357
|
FINISHED |
| Object | majority 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: majority language | Statement: [Kho, languageStatusInChitral, majority language]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languageStatusInChitral Context triple: [Kho, languageStatusInChitral, majority language]
-
A.
ethnicLanguageStatus
Indicates the status or role of a language in relation to a particular ethnic group (e.g., primary, secondary, heritage, or minority language).
-
B.
linguisticStatusOfArea
Indicates the linguistic status or condition that characterizes a particular geographic area.
-
C.
spokenInCanton
Indicates that something (typically a language, phrase, or communication) is expressed using the Cantonese dialect.
-
D.
localLanguageStatus
chosen
Indicates the status or condition of a language as used within a specific local or regional context.
-
E.
regionLanguageStatusInDagestan
Indicates the status or role that a language holds within a specific region of Dagestan (e.g., official, minority, or regional use).
- 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_69f76f02a6c48190a94f3c0b3ee90cf2 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a01d7b3ce8c8190b2f90be730505765 |
completed | May 11, 2026, 1:20 p.m. |
| PD | Predicate disambiguation | batch_6a01d5115a6c8190a6d9f96ec484135a |
completed | May 11, 2026, 1:09 p.m. |
Created at: May 3, 2026, 4:21 p.m.