Triple

T3852227
Position Surface form Disambiguated ID Type / Status
Subject JSC E85321 entity
Predicate coordinatesMissionControlFor P51953 FINISHED
Object crewed NASA missions 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: crewed NASA missions | Statement: [JSC, coordinatesMissionControlFor, crewed NASA missions]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: coordinatesMissionControlFor
Context triple: [JSC, coordinatesMissionControlFor, crewed NASA missions]
  • A. coordinateLocation
    Indicates that an entity is located at, or associated with, a specific geographic coordinate or set of coordinates.
  • B. coordinateRoleWith
    Indicates that one entity aligns, synchronizes, or collaborates its role or responsibilities with those of another entity.
  • C. coordinatesMode
    Indicates that one entity specifies or controls the coordinate system or reference frame used to interpret the spatial data of another entity.
  • D. coordinatesWith
    Indicates that one entity works together with another in an organized or synchronized manner to achieve a shared or compatible outcome.
  • E. coordinateThrough
    Indicates a relationship where one entity organizes or manages interactions, actions, or information by using another entity as the medium, channel, or intermediary through which the coordination occurs.
  • F. None of above. chosen

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_69aed936de1c81908f91bed80f70abb2 completed March 9, 2026, 2:29 p.m.
NER Named-entity recognition batch_69aeec01f7b48190ba1ec89328b3fccb completed March 9, 2026, 3:49 p.m.
PD Predicate disambiguation batch_69aee750377c8190af70c79768c0edd8 completed March 9, 2026, 3:29 p.m.
PDg Predicate description generation batch_69aee8d9b328819080158be59e5bcc97 completed March 9, 2026, 3:35 p.m.
Created at: March 9, 2026, 3:19 p.m.