Triple
T25557625
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 帝国議会 |
E640615
|
entity |
| Predicate | 上院構成原理 |
P36741
|
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.
compositionTypeUpperHouse
chosen
Indicates the method or basis by which the members of an upper legislative house are constituted or selected.
-
B.
votingSystemUpperHouse
Indicates a relationship where a specified voting system is used to elect or constitute the members of an upper legislative house.
-
C.
upperHouse
Indicates that one entity functions as the higher or upper legislative chamber in relation to a given political or governmental system.
-
D.
higherLevelParliament
Indicates that one parliamentary body holds a superior or higher hierarchical level of authority relative to another parliamentary body.
-
E.
parliamentaryHouse
Indicates that one entity functions as a parliamentary chamber or house within the legislative system of another entity.
- 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.