Triple
T37522955
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HMS Royal Sovereign (1786) |
E932828
|
entity |
| Predicate | engagedEnemyShip |
P47243
|
FINISHED |
| Object | Santa Ana |
—
|
NE NERFINISHED |
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: Santa Ana | Statement: [HMS Royal Sovereign (1786), engagedEnemyShip, Santa Ana]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: engagedEnemyShip Context triple: [HMS Royal Sovereign (1786), engagedEnemyShip, Santa Ana]
-
A.
engagedEnemyShips
chosen
Indicates that one or more entities have actively attacked, exchanged fire with, or otherwise entered into direct combat with enemy ships.
-
B.
finalEngagementOpponentShip
Indicates that a ship is the opposing vessel faced in the final engagement or battle.
-
C.
attackedByVessel
Indicates that an entity is the target of an attack carried out by a vessel (such as a ship or boat).
-
D.
capturedShip
Indicates that one party has taken control of another party's ship, typically by force or seizure.
-
E.
commanderOfAttackedShip
Indicates that one entity is the commanding officer of a ship that is the target of an attack.
- 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_69f76ec8862c8190bfa24145f5480642 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fba5eec0448190a5e6f0c43fdcd0e3 |
completed | May 6, 2026, 8:34 p.m. |
| PD | Predicate disambiguation | batch_69fba34edd548190bfa980e6e16e0a88 |
completed | May 6, 2026, 8:23 p.m. |
Created at: May 3, 2026, 4:17 p.m.