Triple
T27852182
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Orakzai |
E703982
|
entity |
| Predicate | associatedLanguageDialect |
P73835
|
FINISHED |
| Object | Central Pashto |
—
|
NE NERFINISHED |
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: Central Pashto | Statement: [Orakzai, associatedLanguageDialect, Central Pashto]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedLanguageDialect Context triple: [Orakzai, associatedLanguageDialect, Central Pashto]
-
A.
languageBranchOfDialectSpoken
Indicates that one language branch is the higher-level linguistic group from which a given spoken dialect originates or to which that dialect belongs.
-
B.
hasPrimaryLanguageDialect
Indicates that an entity’s main or default language is a specific dialect of a broader language.
-
C.
consideredDialectOf
chosen
Indicates that one language variety is regarded as a dialect of another language or linguistic standard.
-
D.
linguisticVariant
Indicates that one linguistic form is an alternative version or expression of another within the same or closely related language context.
-
E.
recognizedRegionalLanguage
Indicates that a language holds officially recognized status within a specific region or subnational jurisdiction.
- 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_69ef840e614c8190a88cf9638c14a265 |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_6a00776c4ebc8190899005fda34234d5 |
completed | May 10, 2026, 12:17 p.m. |
| PD | Predicate disambiguation | batch_6a0076f8a4c4819093ed577e67aa38f9 |
completed | May 10, 2026, 12:15 p.m. |
Created at: April 27, 2026, 6:11 p.m.