Triple
T28571570
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yi family |
E723125
|
entity |
| Predicate | laterTitleOfHead |
P22452
|
FINISHED |
| Object | Emperor of Korea |
—
|
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: Emperor of Korea | Statement: [Yi family, laterTitleOfHead, Emperor of Korea]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterTitleOfHead Context triple: [Yi family, laterTitleOfHead, Emperor of Korea]
-
A.
laterRulerTitle
Indicates that an entity held a particular ruler title at a later point in time, after some earlier status or title.
-
B.
laterTitleHolder
chosen
Indicates that one entity is a subsequent holder of a particular title or position previously held by another entity.
-
C.
laterTitleOfPatron
Indicates that one title held by a patron chronologically succeeds another title previously held by the same patron.
-
D.
laterTitleUsage
Indicates that a title is used or applied to an entity at a later time or in a subsequent context relative to an earlier title usage.
-
E.
laterHonorificTitle
Indicates that an entity is referred to by a particular honorific title at a later time or stage, relative to an earlier form of address.
- 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_69f01d7e97708190ae9e77ee66a68abd |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69fd8e5f7c4c8190ab8e2f2a7bb1bd79 |
completed | May 8, 2026, 7:18 a.m. |
| PD | Predicate disambiguation | batch_69fd8d8a16f08190b9e880901bfa44fe |
completed | May 8, 2026, 7:15 a.m. |
Created at: April 28, 2026, 4:10 a.m.