Triple
T2243123
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kido Butai |
E49440
|
entity |
| Predicate | objectiveAtPearlHarbor |
P19747
|
FINISHED |
| Object | cripple the United States Pacific Fleet |
—
|
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: cripple the United States Pacific Fleet | Statement: [Kido Butai, objectiveAtPearlHarbor, cripple the United States Pacific Fleet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: objectiveAtPearlHarbor Context triple: [Kido Butai, objectiveAtPearlHarbor, cripple the United States Pacific Fleet]
-
A.
objectiveOfJapaneseForces
chosen
Indicates that a specified target, goal, or aim is the military objective pursued by Japanese forces.
-
B.
statusDuringPearlHarbor
Indicates the role, condition, or situation an entity held specifically during the time of the Pearl Harbor attack.
-
C.
UnionObjective
Indicates that an entity has the goal, purpose, or objective of forming, maintaining, or advancing a union or unified organization.
-
D.
objectiveOfUnitedStates
Indicates that something is an official objective or goal pursued by the United States.
-
E.
expeditionObjective
Indicates the primary goal or purpose that an expedition is intended to achieve.
- 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_69a88aa979788190ad6500f1d8eee2fc |
completed | March 4, 2026, 7:40 p.m. |
| NER | Named-entity recognition | batch_69abc0c157e88190a5bc876d9591a24b |
completed | March 7, 2026, 6:08 a.m. |
| PD | Predicate disambiguation | batch_69abbdb160248190aa75b38f11ad8602 |
completed | March 7, 2026, 5:54 a.m. |
Created at: March 4, 2026, 7:47 p.m.