Triple
T8882042
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rauma-class fast attack craft |
E211433
|
entity |
| Predicate | hasModernization |
P4337
|
FINISHED |
| Object | mid-life upgrade |
—
|
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: mid-life upgrade | Statement: [Rauma-class fast attack craft, hasModernization, mid-life upgrade]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasModernization Context triple: [Rauma-class fast attack craft, hasModernization, mid-life upgrade]
-
A.
modernizationType
Indicates the specific kind or category of modernization applied to an entity or system.
-
B.
modernization
chosen
Indicates a process by which something is updated, reformed, or transformed to align with contemporary standards, technologies, or practices.
-
C.
modernizationFeatures
Indicates that something includes characteristics, elements, or improvements associated with making it more modern or up to date.
-
D.
modernizedFor
Indicates that something has been updated, adapted, or improved to suit more recent standards, technologies, or conditions.
-
E.
isModern
Indicates that something belongs to, reflects, or is characteristic of the contemporary or recent period, especially in style, design, or thinking.
- 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.