Triple
T2153399
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 5th Carrier Division |
E47831
|
entity |
| Predicate | roleInPearlHarborAttack |
P6550
|
FINISHED |
| Object | provided carrier-based air strike groups |
—
|
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: provided carrier-based air strike groups | Statement: [5th Carrier Division, roleInPearlHarborAttack, provided carrier-based air strike groups]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInPearlHarborAttack Context triple: [5th Carrier Division, roleInPearlHarborAttack, provided carrier-based air strike groups]
-
A.
roleAtPearlHarbor
chosen
Indicates the specific role, position, or function an entity held in relation to the events at Pearl Harbor.
-
B.
roleAtBattleOfMidway
Indicates the specific role, position, or function an entity held or performed during the Battle of Midway.
-
C.
dateOfPearlHarborAttackParticipation
Indicates that an entity participated in the attack on Pearl Harbor on December 7, 1941.
-
D.
crewPositionOnHiroshimaMission
Indicates the specific role or duty an individual held as a crew member during the Hiroshima bombing mission.
-
E.
JapaneseAirCommander
Indicates that one entity serves as a Japanese air force commander in relation to another entity 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_69a88a1d1fd8819088b34990d69a712f |
completed | March 4, 2026, 7:38 p.m. |
| NER | Named-entity recognition | batch_69abbe4a3b608190b3bd5d8e28534090 |
completed | March 7, 2026, 5:57 a.m. |
| PD | Predicate disambiguation | batch_69abbd9a60648190b20b116be5c7ad98 |
completed | March 7, 2026, 5:54 a.m. |
Created at: March 4, 2026, 7:44 p.m.