Triple
T18567725
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 東久邇宮内閣 |
E453797
|
entity |
| Predicate | dissolvedForCause |
P42155
|
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: [東久邇宮内閣, dissolvedForCause, 連合国軍総司令部による民主化要求への対応困難]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dissolvedForCause Context triple: [東久邇宮内閣, dissolvedForCause, 連合国軍総司令部による民主化要求への対応困難]
-
A.
dissolvedDueTo
chosen
Indicates that a relationship, agreement, or entity came to an end as a result of a specified cause or event.
-
B.
dissolutionResultedIn
Indicates that the process of dissolution of one entity led to the creation, emergence, or transformation into another entity.
-
C.
dissolvedBefore
Indicates that one entity ceased to exist, function, or remain in solution at an earlier time than another entity.
-
D.
dissolvedAlongWith
Indicates that one entity ceased to exist, function, or operate at the same time and in conjunction with another entity.
-
E.
triggerForDissolution
Indicates that one entity serves as the cause or initiating condition that leads to the dissolution or termination of another entity or arrangement.
- 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_69d8d38974308190a9174430ef256b73 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e53affc3e08190b4d16b5ccb0bddbc |
completed | April 19, 2026, 8:28 p.m. |
| PD | Predicate disambiguation | batch_69e478c16e0c8190b03966aa23c395a6 |
completed | April 19, 2026, 6:40 a.m. |
Created at: April 10, 2026, 11:43 a.m.