Triple
T224530
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sōryū |
E4285
|
entity |
| Predicate | operationAtPearlHarbor |
P6532
|
FINISHED |
| Object | launched aircraft against US targets on Oahu |
—
|
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: launched aircraft against US targets on Oahu | Statement: [Sōryū, operationAtPearlHarbor, launched aircraft against US targets on Oahu]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operationAtPearlHarbor Context triple: [Sōryū, operationAtPearlHarbor, launched aircraft against US targets on Oahu]
-
A.
roleAtPearlHarbor
Indicates the specific role, position, or function an entity held in relation to the events at Pearl Harbor.
-
B.
dateOfPearlHarborAttackParticipation
Indicates that an entity participated in the attack on Pearl Harbor on December 7, 1941.
-
C.
notableAirOperation
chosen
Indicates that there is a significant or historically important air operation associated with the subject.
-
D.
aircraftDestroyedUS
Indicates that a U.S. aircraft has been destroyed.
-
E.
aircraftLostByJapan
Indicates that the specified aircraft were lost by Japan, typically through destruction, damage beyond repair, or disappearance.
- 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_69a2573508588190b522c2476d91acfe |
completed | Feb. 28, 2026, 2:47 a.m. |
| NER | Named-entity recognition | batch_69a25dec53ac8190912f3d79576131fa |
completed | Feb. 28, 2026, 3:15 a.m. |
| PD | Predicate disambiguation | batch_69a25b5739dc8190bad8bfa330ce0499 |
completed | Feb. 28, 2026, 3:04 a.m. |
Created at: Feb. 28, 2026, 2:53 a.m.