Triple
T24885904
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of the Komandorski Islands |
E622849
|
entity |
| Predicate | USShipInvolved |
P680
|
FINISHED |
| Object | USS Richmond |
—
|
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: USS Richmond | Statement: [Battle of the Komandorski Islands, USShipInvolved, USS Richmond]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: USShipInvolved Context triple: [Battle of the Komandorski Islands, USShipInvolved, USS Richmond]
-
A.
aircraftCarrierInvolved
Indicates that an aircraft carrier participates in, is present at, or is otherwise directly involved in the specified event or situation.
-
B.
numberOfShipsInvolved
Indicates the total count of ships that participated or were involved in a specified event or situation.
-
C.
shipInvolved
Indicates that a ship participates in, is associated with, or plays a role in a specified event or situation.
-
D.
involvedShipUnitedStates
chosen
Indicates that a ship involved in an event, action, or relationship is associated with or belongs to the United States.
-
E.
shipTypeInvolved
Indicates that a particular type or class of ship is involved or participates in a specified event, situation, or relationship.
- 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_69e2fac4aa848190b3446a3922cec150 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f43043512481909501a3979cac9947 |
completed | May 1, 2026, 4:46 a.m. |
| PD | Predicate disambiguation | batch_69f420fd375c81908ea4a4e60b76ee8f |
completed | May 1, 2026, 3:41 a.m. |
Created at: April 18, 2026, 5:25 a.m.