Triple
T22791349
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USS Helena (CL-113) |
E564117
|
entity |
| Predicate | shipNumberInNameSeries |
P149732
|
FINISHED |
| Object | third U.S. Navy ship named USS Helena |
—
|
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: third U.S. Navy ship named USS Helena | Statement: [USS Helena (CL-113), shipNumberInNameSeries, third U.S. Navy ship named USS Helena]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: shipNumberInNameSeries Context triple: [USS Helena (CL-113), shipNumberInNameSeries, third U.S. Navy ship named USS Helena]
-
A.
shipNumber
Indicates the identifying number assigned to a specific ship.
-
B.
shipNumberInClass
Indicates the specific ordinal position or sequence number that a ship holds within its class.
-
C.
shipName
Indicates the name assigned to a specific ship in the relationship.
-
D.
hullNumber
Indicates the unique identifying number assigned to the hull of a ship or vessel.
-
E.
sailNumber
Indicates the identifying number assigned to a specific sail or sailing vessel, typically used to distinguish it from others.
- 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_69e2458185f88190b0045227ee420411 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17c3545fc819084af67cc25e94839 |
completed | April 29, 2026, 3:34 a.m. |
| PD | Predicate disambiguation | batch_69eed2c32e8c8190b73bb9965ed47d64 |
completed | April 27, 2026, 3:06 a.m. |
| PDg | Predicate description generation | batch_69eeeb5681f88190821129ced752f190 |
completed | April 27, 2026, 4:51 a.m. |
Created at: April 17, 2026, 3:30 p.m.