Triple
T13703940
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USS Intrepid |
E328589
|
entity |
| Predicate | resultOfUSSPhiladelphiaRaid |
P111233
|
FINISHED |
| Object | destruction of USS Philadelphia |
—
|
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: destruction of USS Philadelphia | Statement: [USS Intrepid, resultOfUSSPhiladelphiaRaid, destruction of USS Philadelphia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: resultOfUSSPhiladelphiaRaid Context triple: [USS Intrepid, resultOfUSSPhiladelphiaRaid, destruction of USS Philadelphia]
-
A.
resultOfCommandAtManilaBay
Indicates that something occurs as a consequence of the command issued at the Battle of Manila Bay.
-
B.
resultOfPequotWar
Indicates that the subject entity is an outcome, consequence, or product that occurred as a result of the Pequot War.
-
C.
resultOfRaidOnUmbar
Indicates that something is a consequence or outcome of the raid on Umbar.
-
D.
resultOfBombing
Indicates that something exists or occurs as a consequence or outcome of a bombing event.
-
E.
laterOutcomeOfVoyage
Indicates that one event, state, or outcome occurs as a subsequent result or later phase of a specified voyage.
- F. None of above. chosen
Provenance (4 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_69d8076ff62081908a7bd79889edd7a0 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dcad162158819089280ee1e6b5c2cf |
completed | April 13, 2026, 8:45 a.m. |
| PD | Predicate disambiguation | batch_69dbbe9059488190a8113177c83e1481 |
completed | April 12, 2026, 3:47 p.m. |
| PDg | Predicate description generation | batch_69dbc59ca1a88190a6abd3bd00554c93 |
completed | April 12, 2026, 4:17 p.m. |
Created at: April 9, 2026, 9:54 p.m.