Triple
T29059558
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pacific campaign of USS Essex during the War of 1812 |
E735486
|
entity |
| Predicate | opposingShipsInFinalAction |
P119410
|
FINISHED |
| Object | HMS Phoebe |
—
|
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: HMS Phoebe | Statement: [Pacific campaign of USS Essex during the War of 1812, opposingShipsInFinalAction, HMS Phoebe]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: opposingShipsInFinalAction Context triple: [Pacific campaign of USS Essex during the War of 1812, opposingShipsInFinalAction, HMS Phoebe]
-
A.
finalEngagementOpponentShip
chosen
Indicates that a ship is the opposing vessel faced in the final engagement or battle.
-
B.
numberOfShipsInvolved
Indicates the total count of ships that participated or were involved in a specified event 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.
dispositionOfShips
Indicates the arrangement, allocation, or positioning of ships relative to a plan, location, or situation.
-
E.
opponentFleet
Indicates that one fleet is in an adversarial or opposing relationship to another fleet.
- 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_69f077e85498819088b65186550da8cd |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f72921cf2c8190909bb53f78bcc890 |
completed | May 3, 2026, 10:53 a.m. |
| PD | Predicate disambiguation | batch_69f7283d8cec8190b524c144948bc4ec |
completed | May 3, 2026, 10:49 a.m. |
Created at: April 28, 2026, 10:14 a.m.