Triple
T19277004
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kings of Joseon |
E482081
|
entity |
| Predicate | notableReign |
P111356
|
FINISHED |
| Object | reign of Sejong the Great |
—
|
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: reign of Sejong the Great | Statement: [Kings of Joseon, notableReign, reign of Sejong the Great]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableReign Context triple: [Kings of Joseon, notableReign, reign of Sejong the Great]
-
A.
hasNotableReign
chosen
Indicates that an entity’s period of rule or governance is recognized as particularly significant or noteworthy.
-
B.
notableMonarch
Indicates that the subject is a monarch who is distinguished or historically significant in some notable way.
-
C.
describesReignOf
Indicates that something (such as a text, record, or account) provides information about the period during which a particular ruler or authority was in power.
-
D.
reignTo
Indicates that one entity exercises ruling authority or governance over another entity or domain during a particular period.
-
E.
notableFor
Indicates that an entity is especially recognized or distinguished for a particular quality, achievement, characteristic, or 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_69d8e8ce54cc8190998418ff1f66ef28 |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e5fbbd5f34819086535f28fd880411 |
completed | April 20, 2026, 10:11 a.m. |
| PD | Predicate disambiguation | batch_69e4dd07a7208190afcd51ba1dc87c33 |
completed | April 19, 2026, 1:47 p.m. |
Created at: April 10, 2026, 1:30 p.m.