Triple
T9748322
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jeolla dialect |
E236372
|
entity |
| Predicate | undergoingChange |
P9472
|
FINISHED |
| Object | influence from standard Korean |
—
|
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: influence from standard Korean | Statement: [Jeolla dialect, undergoingChange, influence from standard Korean]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: undergoingChange Context triple: [Jeolla dialect, undergoingChange, influence from standard Korean]
-
A.
undergoing
chosen
Indicates that an entity is currently experiencing, being subjected to, or in the process of a particular action, change, or treatment.
-
B.
changesEvery
Indicates that one entity undergoes a change whenever or each time another specified condition, event, or entity changes.
-
C.
changedFrom
Indicates that an entity previously had one state, value, or form and was altered or updated from that prior condition to a new one.
-
D.
transition
Indicates a change of state or condition from one form, phase, or situation to another.
-
E.
underwent
Indicates that an entity experienced or was subjected to a process, event, or change, typically as the patient of an action.
- 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.