Triple
T25557610
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 帝国議会 |
E640615
|
entity |
| Predicate | 設置国体制 |
P220
|
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.
typeOfGovernmentAfter
Indicates the form of government that exists or is established in a place following a specified event or time period.
-
B.
typeOfPolity
Indicates that one entity is a political unit and the other specifies the kind or classification of that polity (e.g., empire, kingdom, republic).
-
C.
typeOfSelfGovernment
Indicates the specific form or system of self-governance exercised by an entity, such as its degree or structure of political autonomy.
-
D.
treatySystem
Indicates a formal relationship in which entities are bound together by a treaty or set of treaties that regulate their mutual rights, obligations, or interactions.
-
E.
governmentType
chosen
Indicates the form or system of governance under which an entity (such as a country or organization) is organized and ruled.
- 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_69e75dc1beb08190bac7d76b8d6e7bc4 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f8cb186c819099b247e4a8cbd367 |
completed | May 2, 2026, 1:14 p.m. |
| PD | Predicate disambiguation | batch_69f468421ba08190880eac99135e5970 |
completed | May 1, 2026, 8:45 a.m. |
Created at: April 21, 2026, 3:44 p.m.