Triple
T8405340
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USS Essex |
E198482
|
entity |
| Predicate | hullNumber |
P3152
|
FINISHED |
| Object | CV-9 |
E398331
|
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: CV-9 | Statement: [USS Essex, hullNumber, CV-9]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: CV-9 Context triple: [USS Essex, hullNumber, CV-9]
-
A.
CV-9
chosen
CV-9 is the hull number of USS Essex, a World War II-era Essex-class aircraft carrier of the United States Navy that played a major role in Pacific Theater operations.
-
B.
C-9
C-9 is a mountain railway line of Madrid’s Cercanías commuter rail network that connects the city with the Sierra de Guadarrama, including the Puerto de Navacerrada and Cotos areas.
-
C.
CV-4
CV-4 is the hull number of USS Ranger, the first U.S. Navy aircraft carrier designed and built from the keel up as a carrier.
-
D.
CV-3
CV-3 was the hull classification symbol for USS Saratoga, a pioneering U.S. Navy aircraft carrier that served prominently from the interwar period through World War II.
-
E.
CVS-9
CVS-9 was the anti-submarine warfare aircraft carrier designation of the World War II-era Essex-class carrier USS Essex after its postwar reclassification.
- 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_69ca8310df9c8190b25f16161cca3e41 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cb83116bf48190894bd5d5465520ef |
completed | March 31, 2026, 8:17 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ce02f8596c8190a61b6f1ffd5a609c |
completed | April 2, 2026, 5:47 a.m. |
Created at: March 30, 2026, 6:05 p.m.