Triple
T26045680
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USS Wilmington (CL-79) |
E647820
|
entity |
| Predicate | hullConvertedInto |
P21289
|
FINISHED |
| Object | USS Cabot (CVL-28) |
—
|
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: USS Cabot (CVL-28) | Statement: [USS Wilmington (CL-79), hullConvertedInto, USS Cabot (CVL-28)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hullConvertedInto Context triple: [USS Wilmington (CL-79), hullConvertedInto, USS Cabot (CVL-28)]
-
A.
hullTypeConvertedFrom
Indicates that one hull type has been changed or transformed from another original hull type.
-
B.
hullConstruction
Indicates the process or activity of building, assembling, or forming the main body (hull) of a vessel or similar structure.
-
C.
hullOrigin
Indicates the original source, location, or context from which a hull (such as a vessel’s or structure’s main body) is derived or constructed.
-
D.
usedHullNumberSystem
Indicates that an entity employed a hull numbering system to identify or classify ships or vessels.
-
E.
conversionOfShip
chosen
Indicates the process by which a ship is altered or transformed from one configuration, role, or specification into another.
- 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_69e77e8d419481908004e6318d28aaab |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f6065a844c81908e04d361469aa3c5 |
completed | May 2, 2026, 2:12 p.m. |
| PD | Predicate disambiguation | batch_69f5aff889988190ad10bcf1a280f717 |
completed | May 2, 2026, 8:04 a.m. |
Created at: April 22, 2026, 9:10 a.m.