Triple

T34643535
Position Surface form Disambiguated ID Type / Status
Subject Surveyor 3 landing site E889633 entity
Predicate approachTrajectory P6174 FINISHED
Object targeted by Apollo 12 for precision landing 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: targeted by Apollo 12 for precision landing | Statement: [Surveyor 3 landing site, approachTrajectory, targeted by Apollo 12 for precision landing]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: approachTrajectory
Context triple: [Surveyor 3 landing site, approachTrajectory, targeted by Apollo 12 for precision landing]
  • A. trajectoryAssist
    Indicates assistance provided in planning, adjusting, or optimizing the path or course of motion of an entity.
  • B. approachRoute chosen
    Indicates the path or method taken by one entity as it moves toward or comes closer to another entity or target.
  • C. hasApproachTrail
    Indicates that there is a designated trail or path providing access or approach to a particular location or feature.
  • D. resultingTrajectory
    Indicates the path or course that emerges as the outcome of a prior motion, interaction, or transformation.
  • E. approachControl
    Indicates that one entity moves closer to another entity in a deliberate or controlled 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_69f349d825c88190bfc6170ac9281260 completed April 30, 2026, 12:23 p.m.
NER Named-entity recognition batch_69ff27b125948190aced0fe0189fd39a completed May 9, 2026, 12:25 p.m.
PD Predicate disambiguation batch_69ff26c30a0481909ef6a54ded851e42 completed May 9, 2026, 12:21 p.m.
Created at: May 1, 2026, 2:04 a.m.