Triple
T762206
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yamato |
E16094
|
entity |
| Predicate | finalMission |
P68
|
FINISHED |
| Object | suicide surface attack on Allied forces at Okinawa |
—
|
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: suicide surface attack on Allied forces at Okinawa | Statement: [Yamato, finalMission, suicide surface attack on Allied forces at Okinawa]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: finalMission Context triple: [Yamato, finalMission, suicide surface attack on Allied forces at Okinawa]
-
A.
finalStep
Indicates that an action or state represents the last step or concluding stage in a process or sequence.
-
B.
mission
chosen
Indicates that an entity is assigned or engaged in a specific task, operation, or purpose-directed undertaking.
-
C.
missionStart
Indicates the point in time or event at which a mission or task officially begins.
-
D.
missionExtension
Indicates that an existing mission is being prolonged beyond its originally planned duration or scope.
-
E.
finalCity
Indicates that a given city is the last or ultimate city associated with an entity within a sequence, process, or journey.
- 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_69a493684ee48190bd43b7c78da4aec8 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a6841f388190a6d08c3bf5c17fe4 |
completed | March 1, 2026, 8:50 p.m. |
| PD | Predicate disambiguation | batch_69a4a5048a8081908d0542214142664a |
completed | March 1, 2026, 8:43 p.m. |
Created at: March 1, 2026, 7:37 p.m.