Triple
T22791353
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USS Helena (CL-113) |
E564117
|
entity |
| Predicate | plannedPropulsionClass |
P135414
|
FINISHED |
| Object | Cleveland-class cruiser propulsion system |
—
|
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 cruiser propulsion system | Statement: [USS Helena (CL-113), plannedPropulsionClass, Cleveland-class cruiser propulsion system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: plannedPropulsionClass Context triple: [USS Helena (CL-113), plannedPropulsionClass, Cleveland-class cruiser propulsion system]
-
A.
plannedPropulsionType
chosen
Indicates the type of propulsion system that is intended or scheduled to be used for an object or vehicle.
-
B.
propulsionFeature
Indicates a relationship where a propulsion-related characteristic or capability is attributed to an entity.
-
C.
propulsionRole
Indicates the specific function or responsibility an entity has within a propulsion system or propulsion-related process.
-
D.
currentPropulsionSystem
Indicates the propulsion system that an entity is presently using or equipped with.
-
E.
shipClass
Indicates the classification or type category to which a particular ship belongs.
- 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_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. |
Created at: April 17, 2026, 3:30 p.m.