Triple
T22031849
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Queen Soheon |
E544104
|
entity |
| Predicate | marriageToSejongYear |
P146348
|
FINISHED |
| Object | before his accession in 1418 |
—
|
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: before his accession in 1418 | Statement: [Queen Soheon, marriageToSejongYear, before his accession in 1418]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: marriageToSejongYear Context triple: [Queen Soheon, marriageToSejongYear, before his accession in 1418]
-
A.
marriageToWanliYear
Indicates the year in which an entity entered into marriage with Wanli.
-
B.
marriageFormedBy
Indicates that a marriage relationship was created or brought into existence by a specific event, action, or process.
-
C.
marriageToFrancisIOfAustriaStart
Indicates the point in time when an entity’s marriage to Francis I of Austria begins.
-
D.
marriedToEmperor
Indicates that one entity is the spouse of an emperor, signifying a marital relationship to a reigning or titled emperor.
-
E.
formedByMarriageOf
Indicates that something (typically a family, union, or legal entity) comes into existence as a result of the marriage between two entities.
- 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_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. |
| PDg | Predicate description generation | batch_69e6fad4a540819096cdd5ea08527220 |
completed | April 21, 2026, 4:19 a.m. |
Created at: April 16, 2026, 8:24 p.m.