Triple
T26968426
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 岸田文雄内閣 |
E679236
|
entity |
| Predicate | 行政権の所在 |
P161400
|
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.
overallPoliticalAuthority
Indicates that one entity holds ultimate governing power or supreme decision-making control over the political actions and policies of another entity.
-
B.
seatOfGovernmentBranch
Indicates the branch or division of government for which a particular location serves as the seat of authority or administration.
-
C.
mainGovernment
Indicates that one entity serves as the primary governing authority or central government for another entity.
-
D.
seatOfSovereignty
Indicates that a location serves as the primary center of governing authority or ruling power for a political entity.
-
E.
seatOfFederalPowers
Indicates that a location serves as the primary center where a country's federal governmental authorities exercise their official powers and functions.
- 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_69eeeb4f3a448190b1e94b2d4776c16e |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69f621233f2c81908c237f20c50c2ba3 |
completed | May 2, 2026, 4:06 p.m. |
| PD | Predicate disambiguation | batch_69f611af72ac819094598dd2530d7411 |
completed | May 2, 2026, 3:01 p.m. |
| PDg | Predicate description generation | batch_69f6125e54e0819088ee33a20efcc9e6 |
completed | May 2, 2026, 3:03 p.m. |
Created at: April 27, 2026, 6:37 a.m.