Triple
T25557620
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 帝国議会 |
E640615
|
entity |
| Predicate | 政治体制上の位置づけ |
P103899
|
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.
constitutionalPosition
Indicates the official role, office, or status an entity holds within a constitutional or legal framework.
-
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.
associatedPoliticalSystem
chosen
Indicates that there exists a political system with which the subject is formally or conceptually connected.
-
D.
governsInPoliticalSystem
Indicates that one entity exercises authoritative control or rule over another entity within a specified political system or structure.
-
E.
politicalFramework
Indicates the overarching system of political structures, principles, and rules that organize and govern relationships and decision-making within a society or institution.
- 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_69f480789be08190ab252a6de3797200 |
completed | May 1, 2026, 10:29 a.m. |
Created at: April 21, 2026, 3:44 p.m.