Triple
T26215217
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | V-class destroyer |
E655602
|
entity |
| Predicate | typicalPropulsionLayout |
P19520
|
FINISHED |
| Object | twin-screw |
—
|
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: twin-screw | Statement: [V-class destroyer, typicalPropulsionLayout, twin-screw]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalPropulsionLayout Context triple: [V-class destroyer, typicalPropulsionLayout, twin-screw]
-
A.
propulsionLayout
chosen
Indicates how propulsion components are arranged or configured relative to each other within a system.
-
B.
propulsionTypeOfSystem
Indicates the type of propulsion mechanism that a system uses to generate thrust or movement.
-
C.
plannedPropulsionType
Indicates the type of propulsion system that is intended or scheduled to be used for an object or vehicle.
-
D.
propulsionTypeCode
Indicates the specific method or system by which an object or vehicle is propelled or driven.
-
E.
propulsionTypeVariant
Indicates a relationship where one propulsion type is a specific variant or subtype of another propulsion type.
- 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_69ee5b49adb4819086545280d4ef6337 |
completed | April 26, 2026, 6:36 p.m. |
| NER | Named-entity recognition | batch_69fe68a4b67881909ca1d9f276f922e0 |
completed | May 8, 2026, 10:50 p.m. |
| PD | Predicate disambiguation | batch_69fe680234c88190b01f953987b74972 |
completed | May 8, 2026, 10:47 p.m. |
Created at: April 26, 2026, 8:54 p.m.