Triple
T20912058
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 参院 |
E514972
|
entity |
| Predicate | 解散制度 |
P141656
|
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.
disbandedDueTo
Indicates that an organization, group, or entity ceased to exist specifically as a result of a particular cause, event, or condition.
-
B.
reasonForDisbandment
Indicates the cause or circumstance that led to a group, organization, or entity being dissolved or disbanded.
-
C.
endedByDissolution
Indicates that a relationship, agreement, or entity was terminated specifically through a formal dissolution process.
-
D.
disbandsAfter
Indicates that one entity ceases to exist or formally dissolves at some point following the occurrence or completion of another entity or event.
-
E.
eventAfterDissolution
Indicates that one event occurs after the dissolution or termination of another entity, such as an organization, agreement, or relationship.
- F. None of above. chosen
Provenance (4 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. |
| PDg | Predicate description generation | batch_69e5d53d22d08190bc17ed4bed53804a |
completed | April 20, 2026, 7:26 a.m. |
Created at: April 16, 2026, 12:48 p.m.