Triple

T32330072
Position Surface form Disambiguated ID Type / Status
Subject Station 5 E826025 entity
Predicate relatedMissionEvent P93648 FINISHED
Object Apollo 17 landing in Taurus–Littrow E46983 NE 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: Apollo 17 landing in Taurus–Littrow | Statement: [Station 5, relatedMissionEvent, Apollo 17 landing in Taurus–Littrow]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: relatedMissionEvent
Context triple: [Station 5, relatedMissionEvent, Apollo 17 landing in Taurus–Littrow]
  • A. relatedMission
    Indicates that one mission is connected or associated with another mission in a meaningful way, such as by shared goals, context, participants, or timeline.
  • B. relatedMilitaryEvent
    Indicates that two or more entities are connected through the same military event, operation, or conflict, such that one is contextually or causally related to that military occurrence involving the other.
  • C. significantEventInvolves chosen
    Indicates that a significant event includes or engages a particular entity as a participant or key element.
  • D. beyondMissionAssociatedWith
    Indicates a relationship where something is connected or linked to a mission in a way that extends beyond the mission’s core or primary scope.
  • E. relatedExpedition
    Indicates that one expedition has a connection or association with another expedition, such as being part of the same project, time period, or thematic context.
  • F. None of above.

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_69f34913d9048190befaa634025232be completed April 30, 2026, 12:20 p.m.
NER Named-entity recognition batch_6a037c894b488190bcbec2eccaff4a01 completed May 12, 2026, 7:16 p.m.
NED1 Entity disambiguation (via context triple) batch_6a33e89b9a4c8190a65e3ac7e74296f7 completed June 18, 2026, 12:46 p.m.
PD Predicate disambiguation batch_6a0379edf2d88190b492fca86ed23cac completed May 12, 2026, 7:05 p.m.
Created at: May 1, 2026, 12:47 a.m.