Triple
T8643476
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Behdini |
E204711
|
entity |
| Predicate | primaryStatusInRegion |
P33417
|
FINISHED |
| Object | major vernacular of Dohuk area |
—
|
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: major vernacular of Dohuk area | Statement: [Behdini, primaryStatusInRegion, major vernacular of Dohuk area]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryStatusInRegion Context triple: [Behdini, primaryStatusInRegion, major vernacular of Dohuk area]
-
A.
statusInRegion
chosen
Indicates the specific status or condition an entity holds within a particular geographic or administrative region.
-
B.
regionStatus
Indicates the current condition, classification, or operational state assigned to a specific geographic or administrative region.
-
C.
primaryStatus
Indicates the main or most important status assigned to an entity among potentially multiple statuses.
-
D.
primaryTerritory
Indicates that a specified area or region is the main or most important territory associated with an entity.
-
E.
principalState
Indicates that an entity serves as the primary or main state associated with another entity or context.
- 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_69ca834ca1c88190a11ffb0200342fac |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc4798852881909c03c5eadf805e49 |
completed | March 31, 2026, 10:15 p.m. |
| PD | Predicate disambiguation | batch_69cc455d6d448190a2da2a319ac78c37 |
completed | March 31, 2026, 10:06 p.m. |
Created at: March 30, 2026, 6:28 p.m.