Triple
T4189336
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 東條 英機 |
E88993
|
entity |
| Predicate | 関与した作戦 |
P5667
|
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.
involvedUnit
Indicates that a particular unit (such as a group, organization, or division) participates in, is associated with, or plays a role in the referenced event or activity.
-
B.
associatedOperation
chosen
Indicates that one entity is linked to or involved with a particular operation, process, or activity.
-
C.
involvedAirborneOperations
Indicates that an entity participated in or conducted military operations involving the use of aircraft to deploy or support forces.
-
D.
SovietOperation
Indicates that an operation, mission, or organized activity is conducted by, on behalf of, or under the authority of the Soviet Union or its institutions.
-
E.
warParticipatedIn
Indicates that an entity took part as a combatant or active participant in a specific war or armed conflict.
- 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_69aed9569a4481908b6c1fcec2a11e21 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69af04b009dc8190abda3f149a5b16fa |
completed | March 9, 2026, 5:34 p.m. |
| PD | Predicate disambiguation | batch_69af01935064819096b7619f42e164dd |
completed | March 9, 2026, 5:21 p.m. |
Created at: March 9, 2026, 3:46 p.m.