Triple
T23578538
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Korea |
E582133
|
entity |
| Predicate | traditionalScriptCreatedBy |
P59201
|
FINISHED |
| Object | Sejong the Great |
—
|
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: Sejong the Great | Statement: [Korea, traditionalScriptCreatedBy, Sejong the Great]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionalScriptCreatedBy Context triple: [Korea, traditionalScriptCreatedBy, Sejong the Great]
-
A.
formerScript
Indicates that an entity previously served as the script or writing system for another entity, but is no longer used in that role.
-
B.
writingSystemCreator
chosen
Indicates that one entity is the creator or originator of the writing system used by another entity.
-
C.
isWrittenWith
Indicates that something is created or expressed using a particular writing tool, medium, or system.
-
D.
creatorNameInOriginalScript
Indicates that the relationship specifies the name of the creator written in the original script or writing system used by that creator.
-
E.
traditionalAuthor
Indicates that an entity is regarded as the conventional or historically accepted author of a work, even if actual authorship may be uncertain or disputed.
- 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.