Triple
T9178231
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Imperial Japanese Navy submarine I-19 |
E220254
|
entity |
| Predicate | dateOfNotableAttack |
P4332
|
FINISHED |
| Object | 1942-09-15 |
—
|
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: 1942-09-15 | Statement: [Imperial Japanese Navy submarine I-19, dateOfNotableAttack, 1942-09-15]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dateOfNotableAttack Context triple: [Imperial Japanese Navy submarine I-19, dateOfNotableAttack, 1942-09-15]
-
A.
attackDate
chosen
Indicates the calendar date on which an attack or assault event took place.
-
B.
dateOfTragedy
Indicates the specific calendar date on which a tragic event occurred.
-
C.
dateOfNorthernAssault
Indicates the specific date on which a northern assault or attack took place.
-
D.
dateOfMajorKamikazeAttack
Indicates the specific calendar date on which a major kamikaze attack occurred.
-
E.
attackedIn
Indicates that one entity carried out an attack in the location, context, or time frame specified by another entity or value.
- 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_69ca83e589948190ac9907819db11ddf |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69ccc24eeb988190af82dfba49aac2f8 |
completed | April 1, 2026, 6:59 a.m. |
| PD | Predicate disambiguation | batch_69cc660761d88190ab6134b43b376964 |
completed | April 1, 2026, 12:25 a.m. |
Created at: March 30, 2026, 7:23 p.m.