Triple

T27655017
Position Surface form Disambiguated ID Type / Status
Subject Zarya Functional Cargo Block E696969 entity
Predicate roleInAssemblySequence P187787 FINISHED
Object first ISS module launched 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: first ISS module launched | Statement: [Zarya Functional Cargo Block, roleInAssemblySequence, first ISS module launched]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: roleInAssemblySequence
Context triple: [Zarya Functional Cargo Block, roleInAssemblySequence, first ISS module launched]
  • A. roleInAssembly
    Indicates the specific function, position, or responsibility an entity holds within a particular assembly or gathering.
  • B. issAssemblySequence
    Indicates that one entity specifies the ordered sequence of assembly steps or components required to construct another entity.
  • C. issAssemblySequenceNumber chosen
    Indicates the ordered position of an item or step within an ISS-related assembly sequence.
  • D. involvedInComplexAssembly
    Indicates that an entity participates in the process of assembling or forming a larger molecular or structural complex.
  • E. isAssemblyOf
    Indicates that one entity is composed of, or formed by assembling, multiple other entities into a whole.
  • 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_69ef590abd3c8190834d0193bde12007 completed April 27, 2026, 12:39 p.m.
NER Named-entity recognition batch_69fd553d7cb881908d243e7a9f30ac85 completed May 8, 2026, 3:15 a.m.
PD Predicate disambiguation batch_69fd514dcb1c81908333c70d7edd79c9 completed May 8, 2026, 2:58 a.m.
Created at: April 27, 2026, 2:33 p.m.