Triple

T2849383
Position Surface form Disambiguated ID Type / Status
Subject Artemis I E63054 entity
Predicate programGoalContext P32840 FINISHED
Object return humans to the Moon 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: return humans to the Moon | Statement: [Artemis I, programGoalContext, return humans to the Moon]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: programGoalContext
Context triple: [Artemis I, programGoalContext, return humans to the Moon]
  • A. strategicGoal
    Indicates that one entity represents a long-term objective or desired outcome that another entity is intentionally aiming to achieve or align actions toward.
  • B. statedAsGoalFor chosen
    Indicates that something has been explicitly declared or identified as a goal for a particular entity or context.
  • C. narrativeGoal
    Indicates that one entity has a desired outcome or objective within a story or narrative context that drives their actions or development.
  • D. normativeGoal
    Indicates that one entity is a desired or prescribed objective, standard, or end state that another entity ought to pursue or realize.
  • E. campaignObjectiveContext
    Indicates the specific situational or strategic context in which a campaign’s objective is defined or pursued.
  • 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_69ab4c407c408190857d25e027155ce9 completed March 6, 2026, 9:50 p.m.
NER Named-entity recognition batch_69abdf41ac24819087c5b72e3b84117c completed March 7, 2026, 8:18 a.m.
PD Predicate disambiguation batch_69abdd0e86808190bcefffafbd3cd441 completed March 7, 2026, 8:08 a.m.
Created at: March 6, 2026, 10:02 p.m.