Triple
T26968430
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 岸田文雄内閣 |
E679236
|
entity |
| Predicate | 政体 |
P103958
|
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.
typeOfPolity
chosen
Indicates that one entity is a political unit and the other specifies the kind or classification of that polity (e.g., empire, kingdom, republic).
-
B.
governmentType
Indicates the form or system of governance under which an entity (such as a country or organization) is organized and ruled.
-
C.
typeOfGovernmentAfter
Indicates the form of government that exists or is established in a place following a specified event or time period.
-
D.
politicalFramework
Indicates the overarching system of political structures, principles, and rules that organize and govern relationships and decision-making within a society or institution.
-
E.
governmentTypeStrengthened
Indicates that the form or structure of a government has been reinforced, consolidated, or made more powerful or stable relative to its previous state.
- 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_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. |
Created at: April 27, 2026, 6:37 a.m.