Triple
T12593589
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yamashiro escort destroyers |
E300671
|
entity |
| Predicate | navalTask |
P39666
|
FINISHED |
| Object | protect capital ship |
—
|
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: protect capital ship | Statement: [Yamashiro escort destroyers, navalTask, protect capital ship]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: navalTask Context triple: [Yamashiro escort destroyers, navalTask, protect capital ship]
-
A.
navalOperations
Indicates involvement in planning, conducting, or supporting military activities carried out by naval forces at sea or from the sea.
-
B.
navalCommand
Indicates a relationship where one entity holds authority to direct, control, or oversee naval forces or maritime military operations involving another entity.
-
C.
navalOperationsBy
Indicates that a set of naval operations is conducted, controlled, or carried out by a specified agent or organization.
-
D.
navalForceTargeted
Indicates that a naval force is selected or designated as the target of an action or operation.
-
E.
navalTacticRole
chosen
Indicates the specific tactical function or role an entity performs within a naval operation or maritime combat 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_69d7bdea2ca881908f379526c13b1145 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d954e6e20481908bca684c4b497c48 |
completed | April 10, 2026, 7:52 p.m. |
| PD | Predicate disambiguation | batch_69d95416cbd88190b2c65196162349bc |
completed | April 10, 2026, 7:48 p.m. |
Created at: April 9, 2026, 5:07 p.m.