Triple
T9748299
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jeolla dialect |
E236372
|
entity |
| Predicate | subdialectOf |
P31853
|
FINISHED |
| Object | Southwestern Korean dialect group |
—
|
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: Southwestern Korean dialect group | Statement: [Jeolla dialect, subdialectOf, Southwestern Korean dialect group]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: subdialectOf Context triple: [Jeolla dialect, subdialectOf, Southwestern Korean dialect group]
-
A.
consideredDialectOf
Indicates that one language variety is regarded as a dialect of another language or linguistic standard.
-
B.
linguisticSubgroup
chosen
Indicates that one linguistic group forms a subordinate or specialized subset within a larger linguistic group or family.
-
C.
hasDialectContinuumWith
Indicates that two languages or dialects are part of a continuous chain of mutually intelligible varieties, without a clear boundary separating them.
-
D.
dialectFamily
Indicates that one dialect belongs to, or is classified under, a particular dialect family.
-
E.
majorDialectOf
Indicates that one dialect is the primary or most prominent dialect associated with a particular language 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_69ca84d3e24481908a476e2231123cf9 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cd9f68f8b88190b44babf5ae17dfef |
completed | April 1, 2026, 10:42 p.m. |
| PD | Predicate disambiguation | batch_69cd03cc128c81908b84ef224f858b4e |
completed | April 1, 2026, 11:38 a.m. |
Created at: March 30, 2026, 8:23 p.m.