Triple

T26803034
Position Surface form Disambiguated ID Type / Status
Subject Rendez-Vous E671149 entity
Predicate trackIntendedForPerformanceInSpace P140424 FINISHED
Object Rendez-Vous VI NE NERFINISHED

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: Rendez-Vous VI | Statement: [Rendez-Vous, trackIntendedForPerformanceInSpace, Rendez-Vous VI]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: trackIntendedForPerformanceInSpace
Context triple: [Rendez-Vous, trackIntendedForPerformanceInSpace, Rendez-Vous VI]
  • A. usedBySpaceMission
    Indicates that an object, technology, or resource is employed or utilized in the context of a specific space mission.
  • B. coordinatesSpaceProgramsFor
    Indicates that one entity organizes, manages, or aligns the space program activities or initiatives of another entity.
  • C. spaceSegment
    Indicates that one entity is a space-based component or portion of a larger system or infrastructure associated with the other entity.
  • D. associatedWithSpacecraft chosen
    Indicates a relationship in which an entity is connected or related in some way to a particular spacecraft, such as by operation, design, mission, or support role.
  • E. namedForSpacecraft
    Indicates that one entity is named after, or in honor of, a specific spacecraft.
  • 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_69eeb31fbd888190a82dac5822e453bc completed April 27, 2026, 12:51 a.m.
NER Named-entity recognition batch_69f62d53ad58819080c5227c7a729d15 completed May 2, 2026, 4:58 p.m.
PD Predicate disambiguation batch_69f62c15952881908a5ea0c25904afec completed May 2, 2026, 4:53 p.m.
Created at: April 27, 2026, 4:24 a.m.