Triple
T28571538
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yi family |
E723125
|
entity |
| Predicate | continuedAsImperialHouseOf |
P178293
|
FINISHED |
| Object | Korean Empire |
—
|
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: Korean Empire | Statement: [Yi family, continuedAsImperialHouseOf, Korean Empire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: continuedAsImperialHouseOf Context triple: [Yi family, continuedAsImperialHouseOf, Korean Empire]
-
A.
continuedUnderMonarch
Indicates that an entity, such as an office, institution, or status, persisted without interruption during the reign of a specified monarch.
-
B.
associatedWithImperialSuccession
Indicates a relationship where an entity is connected to, involved in, or relevant to the process or events of imperial succession.
-
C.
successorInJapan
Indicates that one entity directly follows or replaces another in a role, position, or sequence within the context of Japan.
-
D.
successorDynastyContinuity
Indicates that one dynasty directly continues or succeeds another in a continuous line of rule or authority.
-
E.
hasBranchOfImperialFamily
Indicates that an entity includes or is associated with a specific branch or lineage of an imperial family.
- 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_69f01d7e97708190ae9e77ee66a68abd |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f70e8755a48190931eaa77946f9460 |
completed | May 3, 2026, 8:59 a.m. |
| PD | Predicate disambiguation | batch_69f70abc00848190a1c3f495ef6c8dc6 |
completed | May 3, 2026, 8:43 a.m. |
| PDg | Predicate description generation | batch_69f70e854b9c8190a3416e2189e17742 |
completed | May 3, 2026, 8:59 a.m. |
Created at: April 28, 2026, 4:10 a.m.