Triple
T19071040
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Surayt |
E466789
|
entity |
| Predicate | dialectalVariation |
P1762
|
FINISHED |
| Object | Midyat dialect |
—
|
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: Midyat dialect | Statement: [Surayt, dialectalVariation, Midyat dialect]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dialectalVariation Context triple: [Surayt, dialectalVariation, Midyat dialect]
-
A.
regionalDialect
chosen
Indicates that one entity uses or is associated with a dialect specific to a particular geographic region in relation to another entity.
-
B.
partOfLinguisticVariety
Indicates that one linguistic variety (such as a dialect, register, or style) is a constituent or subset of another, broader linguistic variety.
-
C.
studiesDialectOf
Indicates that one entity engages in the academic or systematic study of a particular dialect associated with another entity.
-
D.
hasDialectContinuumWith
Indicates that two languages or dialects are part of a continuous chain of mutually intelligible varieties, without a clear boundary separating them.
-
E.
dialectStatus
Indicates the status or classification of a language variety as a dialect within a broader linguistic system.
- 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_69d8dd04f4488190b1121cc53ef2bfd6 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5e19ea01c8190b9bb789da32f9a90 |
completed | April 20, 2026, 8:19 a.m. |
| PD | Predicate disambiguation | batch_69e4b99f602881909eeb9c780597e0e6 |
completed | April 19, 2026, 11:16 a.m. |
Created at: April 10, 2026, 12:04 p.m.