Triple
T23579084
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Korea |
E582149
|
entity |
| Predicate | traditionalNameInKorean |
P21030
|
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: [Korea, traditionalNameInKorean, 조선]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionalNameInKorean Context triple: [Korea, traditionalNameInKorean, 조선]
-
A.
nameInKorean
Indicates that an entity’s name is expressed in the Korean language.
-
B.
pairedTraditionalName
Indicates that two entities are associated as a traditional name pair, typically used together or in customary combination within a cultural or naming convention.
-
C.
traditionalLanguageName
chosen
Indicates the name traditionally used in a particular language to refer to the subject entity.
-
D.
hasTraditionalName
Indicates that an entity is associated with a name traditionally used or recognized for it, often rooted in long-standing cultural or historical practice.
-
E.
hanjaName
Indicates that one entity is the Sino-Korean (hanja) written form corresponding to the name of another entity.
- 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_69e248f8d8248190acd5aee77f0d1709 |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1afd7dbe88190b05ff03f952bf7c3 |
completed | April 29, 2026, 7:14 a.m. |
| PD | Predicate disambiguation | batch_69f118bcc0b08190b25a8dddfd461a0e |
completed | April 28, 2026, 8:29 p.m. |
Created at: April 17, 2026, 6:39 p.m.