Triple
T18368106
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USS Minneapolis |
E440102
|
entity |
| Predicate | hullNumber |
P3152
|
FINISHED |
| Object | CA-36 |
—
|
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: CA-36 | Statement: [USS Minneapolis, hullNumber, CA-36]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: CA-36 Context triple: [USS Minneapolis, hullNumber, CA-36]
-
A.
CA-36
chosen
CA-36 was the hull number of USS Minneapolis, a New Orleans-class heavy cruiser that served prominently with the U.S. Navy in the Pacific during World War II.
-
B.
CA-33
CA-33 was the hull classification symbol for USS Portland, a U.S. Navy heavy cruiser that saw extensive service in the Pacific during World War II.
-
C.
CA-32
CA-32 is the hull classification symbol for USS New Orleans, a U.S. Navy heavy cruiser that saw extensive service during World War II.
-
D.
H-36
H-36 is a military designation referring to the H-36 Caracal, a helicopter used for transport and special operations missions.
-
E.
CA-35
CA-35 is the hull classification symbol for USS Indianapolis, a U.S. Navy Portland-class heavy cruiser best known for its World War II service and tragic sinking after delivering components of the first atomic bomb.
- 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_69d8b918221c8190a9f7b563d64ac677 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e5174f5f448190a1fc67d3039aadd9 |
completed | April 19, 2026, 5:56 p.m. |
Created at: April 10, 2026, 10:38 a.m.