Triple
T22031877
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Munjong of Joseon |
E544105
|
entity |
| Predicate | crownPrinceAppointmentYear |
P87924
|
FINISHED |
| Object | 1421 |
—
|
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: 1421 | Statement: [Munjong of Joseon, crownPrinceAppointmentYear, 1421]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: crownPrinceAppointmentYear Context triple: [Munjong of Joseon, crownPrinceAppointmentYear, 1421]
-
A.
appointedCrownPrinceDate
chosen
Indicates the date on which an individual was formally appointed to the position of crown prince.
-
B.
royalDesignationYear
Indicates the year in which an entity was formally granted or recognized with a royal status or designation.
-
C.
reignAsCrownPrinceFrom
Indicates the period during which a person holds and exercises the official status and role of crown prince of a particular realm or title.
-
D.
placedOnThrone
Indicates that an entity is formally elevated to a position of rulership or authority, typically by being seated on a throne.
-
E.
becameCrownPrincessOn
Indicates the date on which an individual assumed the title and role of crown princess.
- 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_69e11e2f98c8819083e11eab90942a78 |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f127edd5b48190a9aeb2840105c181 |
completed | April 28, 2026, 9:34 p.m. |
| PD | Predicate disambiguation | batch_69e6f63b0d048190b241622759aab9de |
completed | April 21, 2026, 3:59 a.m. |
Created at: April 16, 2026, 8:24 p.m.