Triple
T17168942
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jek language |
E416676
|
entity |
| Predicate | statusInAzerbaijan |
P126360
|
FINISHED |
| Object | 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: minority language | Statement: [Jek language, statusInAzerbaijan, minority language]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusInAzerbaijan Context triple: [Jek language, statusInAzerbaijan, minority language]
-
A.
statusInTurkey
Indicates the legal, social, or official condition or standing that an entity holds within the context of Turkey.
-
B.
statusInIran
Indicates the legal, social, or political standing or condition of an entity specifically within the context of Iran.
-
C.
statusInBelarus
Indicates the legal, social, or official standing or condition that an entity has within the context of Belarus.
-
D.
statusInAfghanistan
Indicates the condition, role, or legal standing an entity holds within the context of Afghanistan.
-
E.
statusInRussia
Indicates the legal, social, or operational condition or standing that something or someone has specifically within the context of Russia.
- F. None of above. chosen
Provenance (4 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_69d886d5f34c8190b24564dfaa63f3fb |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3f9173ee48190bc46622c78479603 |
completed | April 18, 2026, 9:35 p.m. |
| PD | Predicate disambiguation | batch_69e3830d2a90819092386717dc56f0e8 |
completed | April 18, 2026, 1:11 p.m. |
| PDg | Predicate description generation | batch_69e3873f62108190966c4e741ebd548d |
completed | April 18, 2026, 1:29 p.m. |
Created at: April 10, 2026, 5:37 a.m.