Triple
T20454146
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gongyang of Goryeo |
E501730
|
entity |
| Predicate | forcedAbdication |
P140161
|
FINISHED |
| Object | true |
—
|
LITERAL FINISHED |
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: true | Statement: [Gongyang of Goryeo, forcedAbdication, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: forcedAbdication Context triple: [Gongyang of Goryeo, forcedAbdication, true]
-
A.
abdicatedInFavorOf
Indicates that one entity has voluntarily renounced a position, role, or right so that another specific entity may assume it.
-
B.
abdicatedFrom
Indicates that a person has formally renounced or given up a position of authority, office, or throne associated with a particular entity or domain.
-
C.
abdicatedDuring
Indicates that a ruler or officeholder gave up their position or authority during a specified event or time period.
-
D.
abdicationStatus
Indicates the status of an entity’s formal renunciation or relinquishment of a position, role, or authority.
-
E.
reasonForAbdication
Indicates the specific cause, motive, or circumstances that led an individual to formally abdicate a position of authority or power.
- 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_69e0b4ad4940819098cf2ff6413574e5 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e68d04ca4081909b428c31d16fca10 |
completed | April 20, 2026, 8:31 p.m. |
| PD | Predicate disambiguation | batch_69e57679eb40819086142df3e39c928e |
completed | April 20, 2026, 12:42 a.m. |
| PDg | Predicate description generation | batch_69e58d766b408190a1d3698145fb6d30 |
completed | April 20, 2026, 2:20 a.m. |
Created at: April 16, 2026, 11:32 a.m.