Triple
T35411611
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hong Ryun |
E1023526
|
entity |
| Predicate | reignOfMonarchServed |
P44641
|
FINISHED |
| Object | King Gongmin of Goryeo |
—
|
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: King Gongmin of Goryeo | Statement: [Hong Ryun, reignOfMonarchServed, King Gongmin of Goryeo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reignOfMonarchServed Context triple: [Hong Ryun, reignOfMonarchServed, King Gongmin of Goryeo]
-
A.
reignOfMonarch
Indicates the period during which a specific monarch holds ruling authority over a realm or territory.
-
B.
servedMonarch
chosen
Indicates that one entity held a position of service, allegiance, or duty under the authority of a particular monarch.
-
C.
reignAssociatedWith
Indicates a relationship where a period of rule or reign is connected to a specific person, position, or governing entity.
-
D.
reignedUnder
Indicates that one entity exercised ruling authority or governance while being subordinate to, or under the higher sovereignty of, another entity.
-
E.
reignIs
Indicates that one entity holds ruling authority or sovereignty over another for a specified period.
- 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_69f76df54bac8190bd0d3b0eb35cda5f |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fd09840ea88190a2e6d7e577ade717 |
completed | May 7, 2026, 9:52 p.m. |
| PD | Predicate disambiguation | batch_69fd064c49988190afadddbd04d7cb94 |
completed | May 7, 2026, 9:38 p.m. |
Created at: May 3, 2026, 4:03 p.m.