Triple
T17194376
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | осетины |
E417308
|
entity |
| Predicate | языковаяПодгруппа |
P31853
|
FINISHED |
| Object | восточноиранские языки |
—
|
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: восточноиранские языки | Statement: [осетины, языковаяПодгруппа, восточноиранские языки]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: языковаяПодгруппа Context triple: [осетины, языковаяПодгруппа, восточноиранские языки]
-
A.
linguisticSubgroup
chosen
Indicates that one linguistic group forms a subordinate or specialized subset within a larger linguistic group or family.
-
B.
usesLanguageSubfamily
Indicates that one entity communicates or operates using a language that belongs to a specified language subfamily.
-
C.
hasPrimaryLanguageSubbranch
Indicates that one language subbranch is the main or principal subbranch associated with a given language or language family.
-
D.
partOfLanguage
Indicates that one linguistic element belongs to, is included within, or is a component of a particular language.
-
E.
vernacularGroup
Indicates a relationship where entities are grouped or associated based on sharing the same vernacular (local or commonly spoken) language.
- 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_69d886d6ba8c819093215917b3d01689 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e42da93bf88190b60b658087779d36 |
completed | April 19, 2026, 1:19 a.m. |
| PD | Predicate disambiguation | batch_69e383141ae0819096acd71683637cbc |
completed | April 18, 2026, 1:11 p.m. |
Created at: April 10, 2026, 5:38 a.m.