Triple
T29085998
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yi |
E734113
|
entity |
| Predicate | foundingMonarchFamilyName |
P77474
|
FINISHED |
| Object | Taejo of Joseon |
—
|
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: Taejo of Joseon | Statement: [Yi, foundingMonarchFamilyName, Taejo of Joseon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: foundingMonarchFamilyName Context triple: [Yi, foundingMonarchFamilyName, Taejo of Joseon]
-
A.
monarchInFamily
Indicates that a member of a family holds (or held) the position of monarch within that family lineage.
-
B.
royalHouseFounder
chosen
Indicates that one entity is the person who founded or established the royal house or dynasty to which the other entity belongs.
-
C.
monarchicalHouse
Indicates that an entity belongs to, is associated with, or is part of a particular royal or monarchical house or dynasty.
-
D.
royalHouseByFather
Indicates that an individual's royal house affiliation is determined through their father's royal lineage.
-
E.
lastRoyalHouseOf
Indicates that one entity is the final ruling royal house or dynasty associated with another entity, such as a realm, title, or political unit.
- 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_69f05b0c0f28819086eae6e84f2ae472 |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69fcda3699948190adb57625bae08091 |
completed | May 7, 2026, 6:30 p.m. |
| PD | Predicate disambiguation | batch_69fcd8fd16d08190b0aca6e19a632e99 |
completed | May 7, 2026, 6:25 p.m. |
Created at: April 28, 2026, 11 a.m.