Triple
T19333368
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aghul |
E483553
|
entity |
| Predicate | statusInDagestan |
P61287
|
FINISHED |
| Object | local minority 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: local minority language | Statement: [Aghul, statusInDagestan, local minority language]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusInDagestan Context triple: [Aghul, statusInDagestan, local minority language]
-
A.
regionLanguageStatusInDagestan
chosen
Indicates the status or role that a language holds within a specific region of Dagestan (e.g., official, minority, or regional use).
-
B.
statusInAzerbaijan
Indicates the legal, political, or social condition or standing that something or someone has within the context of Azerbaijan.
-
C.
statusInDerna
Indicates the specific condition, role, or situation an entity holds within the context of Derna.
-
D.
statusInRussia
Indicates the legal, social, or operational condition or standing that something or someone has specifically within the context of Russia.
-
E.
statusInAfghanistan
Indicates the condition, role, or legal standing an entity holds within the context of Afghanistan.
- 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_69d8e8d13e3c81909d91d1d5ec37c095 |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e61642f49c81909226cfd701f7c139 |
completed | April 20, 2026, 12:04 p.m. |
| PD | Predicate disambiguation | batch_69e4dd12303c8190a2027c062b2dff40 |
completed | April 19, 2026, 1:48 p.m. |
Created at: April 10, 2026, 1:33 p.m.