Triple
T21374452
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HMS Peacock |
E527160
|
entity |
| Predicate | sunkBy |
P4687
|
FINISHED |
| Object | USS Hornet |
—
|
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 Hornet | Statement: [HMS Peacock, sunkBy, USS Hornet]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: USS Hornet Context triple: [HMS Peacock, sunkBy, USS Hornet]
-
A.
USS Hornet
chosen
USS Hornet was a notable early 19th-century United States Navy sloop-of-war that gained fame for its victories during the War of 1812.
-
B.
USS Wasp
USS Wasp was a United States Navy aircraft carrier that served prominently during the mid-20th century, supporting both combat operations and space mission recoveries.
-
C.
USS Wasp
USS Wasp was a prominent warship of the American Revolutionary-era Continental Navy, known for its role in early naval engagements against British forces.
-
D.
USS Yorktown
USS Yorktown was a U.S. Navy aircraft carrier that played a pivotal role in early World War II Pacific battles, most notably the Battle of Midway.
-
E.
USS Lexington
USS Lexington was a prominent warship of the Continental Navy during the American Revolutionary War, known for its early naval engagements against British forces.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e0b51e80808190ba5cb05667af02a9 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e8b0b3666c8190a83bb32eeba24105 |
completed | April 22, 2026, 11:27 a.m. |
Created at: April 16, 2026, 5:10 p.m.