Triple

T7918805
Position Surface form Disambiguated ID Type / Status
Subject Zarya E183891 entity
Predicate powerTransferCapability P29915 FINISHED
Object can transfer electrical power to other ISS modules 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: can transfer electrical power to other ISS modules | Statement: [Zarya, powerTransferCapability, can transfer electrical power to other ISS modules]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: powerTransferCapability
Context triple: [Zarya, powerTransferCapability, can transfer electrical power to other ISS modules]
  • A. transferredPowerTo
    Indicates that one entity has passed control, authority, or energy to another entity.
  • B. maximumPowerDeliveredToPD
    Indicates the highest level of electrical power that can be supplied to the power-drawing device (PD) in this relationship.
  • C. powerBudgetCharacteristic
    Indicates a relationship where an entity’s power consumption limits, allocations, or constraints are specified as a characteristic or parameter.
  • D. powerCharacteristic chosen
    Indicates a relationship where one entity has a specific power-related property, capacity, or performance attribute characterized by the other entity.
  • E. couplingCapability
    Indicates the ability or suitability of one entity to connect, link, or interface with another in a functional or compatible manner.
  • 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_69ca828efbe48190bd48482650182e79 completed March 30, 2026, 2:02 p.m.
NER Named-entity recognition batch_69cb3a8fbbb48190b50def4941761a31 completed March 31, 2026, 3:07 a.m.
PD Predicate disambiguation batch_69cae9316e98819080be7bf1a6ff92f1 completed March 30, 2026, 9:20 p.m.
Created at: March 30, 2026, 5:05 p.m.