Triple
T12650955
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 韓国統監 |
E302155
|
entity |
| Predicate | 対韓国皇室関係 |
P47199
|
FINISHED |
| Object | 韓国皇帝の権限を大幅に制限 |
—
|
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: 韓国皇帝の権限を大幅に制限 | Statement: [韓国統監, 対韓国皇室関係, 韓国皇帝の権限を大幅に制限]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: 対韓国皇室関係 Context triple: [韓国統監, 対韓国皇室関係, 韓国皇帝の権限を大幅に制限]
-
A.
国の元首との関係
Indicates a relationship or connection that an entity has with the head of state of a country.
-
B.
皇位継承順位への関係
Indicates the relationship of an entity to the line of succession to the imperial throne, such as its position, eligibility, or connection within that succession order.
-
C.
familyRelationToEmperor
Indicates that one entity is related to an emperor by family ties, specifying a kinship or familial connection between them.
-
D.
constitutionalMonarchRelation
Indicates that one entity serves as a constitutional monarch in relation to another entity, over which they act as a ceremonial head of state within a constitutional framework.
-
E.
politicalRelation
chosen
Indicates a relationship between entities that involves political alignment, influence, affiliation, conflict, or cooperation within a political context.
- 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_69d7bded71a88190bb76e2413af9ea66 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d9617b07ec8190b714f04ae6654060 |
completed | April 10, 2026, 8:45 p.m. |
| PD | Predicate disambiguation | batch_69d960b78ce8819091f15dd5013e6da5 |
completed | April 10, 2026, 8:42 p.m. |
Created at: April 9, 2026, 5:18 p.m.