Triple
T22533181
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 孝明天皇 |
E557094
|
entity |
| Predicate | 関与した政治運動 |
P24043
|
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.
participatesInPoliticsOf
Indicates involvement or active engagement by one entity in the political processes, affairs, or governance activities of another entity.
-
B.
involvedIndependenceMovement
Indicates that an entity actively participated in or contributed to an independence movement seeking political or national self-determination.
-
C.
involvedPoliticalContext
chosen
Indicates that an entity participated in, was affected by, or is otherwise connected to a particular political situation, environment, or set of political circumstances.
-
D.
associatedWithReformMovement
Indicates that an entity is connected or linked in some way to a reform movement, such as by participation, support, influence, or affiliation.
-
E.
memberOfPoliticalMovement
Indicates that an entity belongs to, supports, or participates in a specific political movement.
- 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_69e11e57483c8190b0887c4f8ff26446 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15ed88cf08190ae7e5b6bf9a80372 |
completed | April 29, 2026, 1:28 a.m. |
| PD | Predicate disambiguation | batch_69e898c864148190a3f5feec7967d49c |
completed | April 22, 2026, 9:45 a.m. |
Created at: April 16, 2026, 8:51 p.m.