Triple
T24151759
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Uiseong Kim clan |
E598553
|
entity |
| Predicate | writingSystemNameInKorean |
P154795
|
FINISHED |
| Object | 의성김씨 |
—
|
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: 의성김씨 | Statement: [Uiseong Kim clan, writingSystemNameInKorean, 의성김씨]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: writingSystemNameInKorean Context triple: [Uiseong Kim clan, writingSystemNameInKorean, 의성김씨]
-
A.
writingSystem
Indicates that one entity is the script or system of written symbols used to represent the language or content of another entity.
-
B.
writingSystemUsedIn
Indicates that a particular writing system is employed for written communication within a given language, region, or context.
-
C.
languageOfKoreanName
Indicates that the specified language is the language in which the given Korean name is expressed or written.
-
D.
writingSystemStandardized
Indicates that a writing system has been formally codified and regulated according to an accepted standard or set of rules.
-
E.
writingSystemDevelopedFor
Indicates that a particular writing system was created or adapted specifically to be used for a given language, community, or purpose.
- F. None of above. chosen
Provenance (4 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_69e288c9e488819093dd1acd91b08b8a |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1e0e108308190ba8740590a1c5130 |
completed | April 29, 2026, 10:43 a.m. |
| PD | Predicate disambiguation | batch_69f176585f3481909beb907de252cd98 |
completed | April 29, 2026, 3:09 a.m. |
| PDg | Predicate description generation | batch_69f1785afe3c81909be28986ffe944bf |
completed | April 29, 2026, 3:17 a.m. |
Created at: April 17, 2026, 11:30 p.m.