Triple
T38602712
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CVS-14 |
E934257
|
entity |
| Predicate | previousHullClassification |
P8335
|
FINISHED |
| Object | CV-14 |
—
|
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: CV-14 | Statement: [CVS-14, previousHullClassification, CV-14]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: previousHullClassification Context triple: [CVS-14, previousHullClassification, CV-14]
-
A.
previousShipClass
Indicates that one ship class directly precedes another in a sequence or lineage of ship classes.
-
B.
hullNumber
Indicates the unique identifying number assigned to the hull of a ship or vessel.
-
C.
previousNavy
Indicates that one entity previously served in, belonged to, or was part of a navy before the current point in time.
-
D.
previousClassification
chosen
Indicates that one classification precedes another in time or in an ordered sequence of classifications.
-
E.
hullNumberPrefix
Indicates that one entity is the prefix portion of the hull number assigned to another entity (typically a vessel or ship).
- F. None of above.
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_69f76ecc17688190b389b693a5927501 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a00144238708190acbec3f791cc873e |
completed | May 10, 2026, 5:14 a.m. |
| PD | Predicate disambiguation | batch_6a00120244a4819090ef39070aba9d99 |
completed | May 10, 2026, 5:05 a.m. |
Created at: May 3, 2026, 4:32 p.m.