Triple
T7179265
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USS Cabot (CVL-28) |
E167402
|
entity |
| Predicate | originalHullType |
P6545
|
FINISHED |
| Object | Cleveland-class light cruiser |
—
|
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: Cleveland-class light cruiser | Statement: [USS Cabot (CVL-28), originalHullType, Cleveland-class light cruiser]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalHullType Context triple: [USS Cabot (CVL-28), originalHullType, Cleveland-class light cruiser]
-
A.
originalShipType
chosen
Indicates the type or category of ship that an entity was originally classified or built as.
-
B.
hullType
Indicates the specific structural design or configuration of an object's hull, typically classifying how its outer body or shell is shaped or constructed.
-
C.
hullConstruction
Indicates the process or activity of building, assembling, or forming the main body (hull) of a vessel or similar structure.
-
D.
hullNumber
Indicates the unique identifying number assigned to the hull of a ship or vessel.
-
E.
usedHullNumberSystem
Indicates that an entity employed a hull numbering system to identify or classify ships or vessels.
- 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_69c6888a7c548190a3d39b52a393080f |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e9b045c48190b27b2d6f7c11026f |
completed | March 27, 2026, 8:33 p.m. |
| PD | Predicate disambiguation | batch_69c6e74fb0f48190b2ad4dd4efdd241a |
completed | March 27, 2026, 8:23 p.m. |
Created at: March 27, 2026, 2:49 p.m.