Triple
T5833809
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USS Hammann (DE-131) |
E129415
|
entity |
| Predicate | hasNamePrefix |
P20540
|
FINISHED |
| Object | USS |
E123727
|
NE 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: USS | Statement: [USS Hammann (DE-131), hasNamePrefix, USS]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: USS Context triple: [USS Hammann (DE-131), hasNamePrefix, USS]
-
A.
USS
chosen
USS is the standard ship prefix used by the United States Navy to denote a commissioned vessel of the U.S. fleet.
-
B.
USS Cassin Young
USS Cassin Young is a preserved World War II-era Fletcher-class destroyer now serving as a museum ship in Boston, Massachusetts.
-
C.
USS Ticonderoga
USS Ticonderoga was a U.S. Navy aircraft carrier that notably served as a recovery ship for several NASA missions, including Apollo 17.
-
D.
USS Ticonderoga
USS Ticonderoga was an American naval vessel that served on Lake Champlain during the War of 1812, playing a key role in securing U.S. victory against the British.
-
E.
USS Torsk
USS Torsk is a World War II-era Tench-class submarine preserved as a museum ship in Baltimore’s Inner Harbor.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69c0084af79c81908af128ccc29983d0 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c0346e6e9c8190a245e5d10595a68f |
completed | March 22, 2026, 6:26 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c0a193ac408190a06159406a814adb |
completed | March 23, 2026, 2:12 a.m. |
Created at: March 22, 2026, 3:54 p.m.