Triple

T16587044
Position Surface form Disambiguated ID Type / Status
Subject Kinsei 45 E402985 entity
Predicate powerOutputCharacteristic P123427 FINISHED
Object improved power output over earlier Kinsei variants 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: improved power output over earlier Kinsei variants | Statement: [Kinsei 45, powerOutputCharacteristic, improved power output over earlier Kinsei variants]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: powerOutputCharacteristic
Context triple: [Kinsei 45, powerOutputCharacteristic, improved power output over earlier Kinsei variants]
  • A. powerOutputW
    Indicates the amount of power produced or delivered by an entity, measured in watts.
  • B. powerOutput_kW
    Indicates the amount of power produced or delivered by something, measured in kilowatts.
  • C. powerOutputType
    Indicates the specific form or category of power output associated with an entity, such as electrical, mechanical, or thermal.
  • D. powerOutputApprox
    Indicates an approximate or estimated value for the power output produced by an entity or system.
  • E. designPowerOutput
    Indicates the intended or specified power output level that something is designed to produce under defined conditions.
  • F. None of above. chosen

Provenance (4 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_69d88387363c8190a97a0c942130de97 completed April 10, 2026, 4:58 a.m.
NER Named-entity recognition batch_69e3599daa508190a9ed6f64138c0e53 completed April 18, 2026, 10:14 a.m.
PD Predicate disambiguation batch_69e296a7d9d0819088555bca6c936e79 completed April 17, 2026, 8:23 p.m.
PDg Predicate description generation batch_69e2d7fb02f481908885a226c2191231 completed April 18, 2026, 1:01 a.m.
Created at: April 10, 2026, 5:16 a.m.