Triple
T35497494
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | King Chungmok of Goryeo |
E1025907
|
entity |
| Predicate | royalHouseThroughMother |
P130169
|
FINISHED |
| Object | Borjigin (Yuan imperial clan) |
—
|
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: Borjigin (Yuan imperial clan) | Statement: [King Chungmok of Goryeo, royalHouseThroughMother, Borjigin (Yuan imperial clan)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: royalHouseThroughMother Context triple: [King Chungmok of Goryeo, royalHouseThroughMother, Borjigin (Yuan imperial clan)]
-
A.
royalHouseOfMother
chosen
Indicates the dynastic or royal family to which an individual's mother belongs.
-
B.
royalHouseByFather
Indicates that an individual's royal house affiliation is determined through their father's royal lineage.
-
C.
heirThroughFemaleLine
Indicates that one entity is the heir of another specifically through a lineage traced via female ancestors.
-
D.
relatedRoyalHouse
Indicates a relationship where one royal house is historically, genealogically, or politically connected to another royal house.
-
E.
parentOfRoyalDescendants
Indicates being the parent of one or more individuals who are of royal descent.
- 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_69f76dfc9c60819089c4217d93922615 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f79da9f80c8190b0afd8509f28747b |
completed | May 3, 2026, 7:10 p.m. |
| PD | Predicate disambiguation | batch_69f79617d40481909ba372f94209c08b |
completed | May 3, 2026, 6:38 p.m. |
Created at: May 3, 2026, 4:04 p.m.