Triple
T5037135
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 永野修身 |
E113452
|
entity |
| Predicate | 関与した出来事 |
P51071
|
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.
hasPeopleInvolved
chosen
Indicates that certain people participate in, are associated with, or are otherwise involved in the referenced entity or event.
-
B.
involvedAction
Indicates that an entity participates in, performs, or is otherwise engaged in a specified action or activity.
-
C.
stillInvolvedIn
Indicates that an entity continues to participate in or be associated with a particular activity, role, or relationship at the present time.
-
D.
involves
Indicates that an entity participates in, is a part of, or is implicated within a particular event, process, or relationship.
-
E.
intervenedIn
Indicates that an entity took action to alter, influence, or interrupt the course of an event, process, or interaction involving other entities.
- 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_69bd44384298819089c49e7c330ec7b8 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd73bb069c8190af86f1b2f95f3d95 |
completed | March 20, 2026, 4:20 p.m. |
| PD | Predicate disambiguation | batch_69bd71529d608190a53470ba6c14bb1d |
completed | March 20, 2026, 4:09 p.m. |
Created at: March 20, 2026, 1:37 p.m.