Triple

T15841740
Position Surface form Disambiguated ID Type / Status
Subject Kockums AB E384116 entity
Predicate knownForTechnology P1485 FINISHED
Object air-independent propulsion 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: air-independent propulsion | Statement: [Kockums AB, knownForTechnology, air-independent propulsion]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: knownForTechnology
Context triple: [Kockums AB, knownForTechnology, air-independent propulsion]
  • A. technologyPioneered
    Indicates that an entity was the first or among the first to develop, introduce, or significantly advance a particular technology.
  • B. associatedWithTechnology chosen
    Indicates a relationship where an entity is connected to, involved with, or utilizes a particular technology.
  • C. namedForKnownFor
    Indicates that one entity is named after another entity specifically because that other entity is notable or recognized for something.
  • D. formerlyKnownFor
    Indicates that an entity was previously recognized or notable for a particular role, attribute, or activity, but is no longer primarily associated with it.
  • E. knownIn
    Indicates that an entity is recognized, acknowledged, or familiar within a particular context, domain, or group.
  • 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_69d86da34c888190976e06c4019d415a completed April 10, 2026, 3:25 a.m.
NER Named-entity recognition batch_69e142e764088190afba6c5c1acf8199 completed April 16, 2026, 8:13 p.m.
PD Predicate disambiguation batch_69e005434ed88190baf11c169da3cf29 completed April 15, 2026, 9:38 p.m.
Created at: April 10, 2026, 4:50 a.m.