Triple
T10318253
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Able-Baker series of tests |
E242074
|
entity |
| Predicate | usedTargetShips |
P880
|
FINISHED |
| Object | decommissioned U.S. Navy vessels |
—
|
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: decommissioned U.S. Navy vessels | Statement: [Able-Baker series of tests, usedTargetShips, decommissioned U.S. Navy vessels]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedTargetShips Context triple: [Able-Baker series of tests, usedTargetShips, decommissioned U.S. Navy vessels]
-
A.
targetedShip
Indicates that one entity has selected or designated a particular ship as the focus of its attention or action, such as for attack, tracking, or interaction.
-
B.
numberOfShips
Indicates the quantity of ships associated with a given entity or situation.
-
C.
engagedEnemyShips
Indicates that one or more entities have actively attacked, exchanged fire with, or otherwise entered into direct combat with enemy ships.
-
D.
effectOnShips
Indicates the impact or influence that one entity, event, or condition has on ships.
-
E.
shipUsed
chosen
Indicates that a particular ship was employed or utilized in carrying out an event, activity, or operation.
- 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_69d381ac38808190a8ca7457c85b625b |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4d7ccb7ec8190a538cf279e48116e |
completed | April 7, 2026, 10:09 a.m. |
| PD | Predicate disambiguation | batch_69d4d1f4f354819080b4ed4bc61bdff6 |
completed | April 7, 2026, 9:44 a.m. |
Created at: April 6, 2026, 11:49 a.m.