Triple
T25294943
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sherani District |
E634190
|
entity |
| Predicate | inferredLanguageMajority |
P11430
|
FINISHED |
| Object | Pashto |
—
|
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: Pashto | Statement: [Sherani District, inferredLanguageMajority, Pashto]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inferredLanguageMajority Context triple: [Sherani District, inferredLanguageMajority, Pashto]
-
A.
majorityLanguageOf
chosen
Indicates that a given language is the primary or most widely spoken language within a specified group, region, or entity.
-
B.
shareMajorLanguage
Indicates that the entities have at least one primary or major language in common.
-
C.
hasOfficialLanguageMajority
Indicates that a specified language is spoken by the majority of the population within a given political or geographic entity.
-
D.
majorityBilingualWith
Indicates that the majority of individuals in a given group or population are bilingual in the two specified languages or language groups.
-
E.
hasDominantNeighborLanguage
Indicates that an entity’s primary neighboring language exerts a dominant influence or holds a superior status over other nearby languages.
- 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_69e75a9503d48190b80a005c6af0cb50 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f48fd1d1c08190ba007255d4527a6d |
completed | May 1, 2026, 11:34 a.m. |
| PD | Predicate disambiguation | batch_69f45d06d0388190b36ecde92013624a |
completed | May 1, 2026, 7:57 a.m. |
Created at: April 21, 2026, 1:22 p.m.