Triple
T19532519
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 山本五十六 |
E488689
|
entity |
| Predicate | 指揮した作戦 |
P67172
|
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.
指揮した戦い
chosen
Indicates a relationship where an entity commanded or directed the course of a specific battle.
-
B.
commandedOperationAgainst
Indicates that one entity issued authoritative orders to initiate or conduct a specific military or strategic operation directed against another entity.
-
C.
militaryOperationName
Indicates the specific named military operation associated with an action, event, or entity.
-
D.
関与作戦
Indicates a relationship where an entity is involved in, participates in, or contributes to the execution of a specific operation or mission.
-
E.
offensiveOperationBy
Indicates that an offensive military or strategic operation is carried out by a specified actor or entity.
- 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_69d8e8db5b6c8190984b61f91981f575 |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e6364091f4819088b27d0ffdf6010d |
completed | April 20, 2026, 2:20 p.m. |
| PD | Predicate disambiguation | batch_69e514c9c00481909b76bda67957e58b |
completed | April 19, 2026, 5:45 p.m. |
Created at: April 10, 2026, 1:41 p.m.