Triple
T8882010
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rauma-class fast attack craft |
E211433
|
entity |
| Predicate | hasPropulsionType |
P14429
|
FINISHED |
| Object | diesel engines |
—
|
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: diesel engines | Statement: [Rauma-class fast attack craft, hasPropulsionType, diesel engines]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPropulsionType Context triple: [Rauma-class fast attack craft, hasPropulsionType, diesel engines]
-
A.
hasPropulsionComponent
Indicates that an entity includes or is equipped with a component responsible for providing propulsion.
-
B.
propulsionTypeTested
Indicates that a specific type of propulsion has been subjected to testing or experimental evaluation.
-
C.
hasMotivePowerType
chosen
Indicates that an entity (such as a vehicle or machine) operates using a specified type of motive power (e.g., electric, diesel, steam).
-
D.
propulsionMedium
Indicates the medium or substance through which propulsion is generated or transmitted for movement.
-
E.
propulsionFeature
Indicates a relationship where a propulsion-related characteristic or capability is attributed to an entity.
- 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_69ca838f9e20819096ab1f236a70381a |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc616a01f48190b8bbde0e898a38c7 |
completed | April 1, 2026, 12:06 a.m. |
| PD | Predicate disambiguation | batch_69cc5c2956788190a311c647b4da17a6 |
completed | March 31, 2026, 11:43 p.m. |
Created at: March 30, 2026, 6:53 p.m.