Triple
T14023232
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | トラ・トラ・トラ |
E337387
|
entity |
| Predicate | 歴史的性格 |
P18777
|
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.
historicalFigure
Indicates that an entity is recognized as a notable person from the past who played a significant role in history.
-
B.
historicalCharacteristic
chosen
Indicates that an entity possesses a trait, feature, or quality that is rooted in or defined by its history or past events.
-
C.
Chronica_subject
Indicates that an entity serves as the subject or main focus of a chronicle, record, or historical account.
-
D.
historicalFate
Indicates that two entities share a common or interconnected outcome, destiny, or consequence within a historical context.
-
E.
historicalPeople
Indicates that the related entities are people who lived in or are associated with a past historical period or context.
- 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_69d81c6543a48190bd5ba93d7419e797 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de2f3d87b88190b038d334f4965369 |
completed | April 14, 2026, 12:12 p.m. |
| PD | Predicate disambiguation | batch_69de05a802ac819090604025aae6a4d5 |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 9, 2026, 10:19 p.m.