Triple
T20912092
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 参院 |
E514972
|
entity |
| Predicate | 国会内の役割 |
P40745
|
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.
parliamentaryRoleIn
chosen
Indicates that an entity holds or has held a specific role, position, or function within a particular parliament or parliamentary body.
-
B.
legislativeRole
Indicates that an entity holds or performs a specific official position, function, or duty within a legislative body or lawmaking process.
-
C.
roleInCongress
Indicates the specific position or function an individual holds within a legislative congress.
-
D.
hasGovernmentBodyRole
Indicates that an entity holds or is assigned a specific role or position within a governmental body or institution.
-
E.
governmentalRole
Indicates that an entity holds or is assigned a specific official position, function, or authority within a government or public administration structure.
- 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_69e0b4f9d5ec8190bb2bd27350ed341c |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6ec5f5bc48190a8e7e6af60b158fb |
completed | April 21, 2026, 3:17 a.m. |
| PD | Predicate disambiguation | batch_69e5c9ac91108190a6700fcdf2f11890 |
completed | April 20, 2026, 6:37 a.m. |
Created at: April 16, 2026, 12:48 p.m.