Triple
T33747745
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jilu district |
E864743
|
entity |
| Predicate | hasDialectSpeakersDiasporaIn |
P27697
|
FINISHED |
| Object | Iraq |
—
|
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: Iraq | Statement: [Jilu district, hasDialectSpeakersDiasporaIn, Iraq]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDialectSpeakersDiasporaIn Context triple: [Jilu district, hasDialectSpeakersDiasporaIn, Iraq]
-
A.
hasNumberOfDialects
Indicates the relationship between a language (or linguistic entity) and the count of distinct dialects it possesses.
-
B.
hasDialectContinuumWith
Indicates that two languages or dialects are part of a continuous chain of mutually intelligible varieties, without a clear boundary separating them.
-
C.
hasNativeSpeakers
Indicates that a language or dialect is spoken as a first language by one or more people or populations.
-
D.
spokenInDiaspora
chosen
Indicates that a language or dialect is used by a community living outside its original homeland or region of origin.
-
E.
hasLanguageInhabitants
Indicates that a particular language is spoken or used by the inhabitants of a specified place or region.
- 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_69f3498c35f881909df279ae4270f831 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fee335cb08819097e3a0e09d5ebf49 |
completed | May 9, 2026, 7:33 a.m. |
| PD | Predicate disambiguation | batch_69fee2c74fd88190acfc045ab07b7f6b |
completed | May 9, 2026, 7:31 a.m. |
Created at: May 1, 2026, 1:45 a.m.