Triple
T9940443
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pyong-il |
E194064
|
entity |
| Predicate | associatedScriptForm |
P16423
|
FINISHED |
| Object | 평일 |
—
|
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: 평일 | Statement: [Pyong-il, associatedScriptForm, 평일]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedScriptForm Context triple: [Pyong-il, associatedScriptForm, 평일]
-
A.
typicalScriptForm
Indicates the usual or standard written script or notation in which something is commonly represented.
-
B.
associatedWithForm
Indicates a relationship in which something is linked or connected to a particular form, document, or structured representation.
-
C.
relatedToScript
chosen
Indicates a general association or connection between an entity and a script, without specifying the exact nature of that relationship.
-
D.
addsScript
Indicates that one entity attaches or incorporates a script (code or instructions) into another entity, enabling additional behavior or functionality.
-
E.
formerScript
Indicates that an entity previously served as the script or writing system for another entity, but is no longer used in that role.
- 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_69ca82e409348190a393777356b80a2a |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cdb60f4ffc8190bfe916bb4a7bf5c5 |
completed | April 2, 2026, 12:19 a.m. |
| PD | Predicate disambiguation | batch_69cd1d9428cc81909b4b4938566d78a7 |
completed | April 1, 2026, 1:28 p.m. |
Created at: March 30, 2026, 8:44 p.m.