Triple

T17541785
Position Surface form Disambiguated ID Type / Status
Subject STS-3 E427215 entity
Predicate callSign P1565 FINISHED
Object Columbia 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: Columbia | Statement: [STS-3, callSign, Columbia]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Columbia
Context triple: [STS-3, callSign, Columbia]
  • A. Columbia
    Columbia is a small unincorporated community located in the state of Iowa in the United States.
  • B. Columbia
    Columbia is a small town located in Brown County in northeastern South Dakota, United States.
  • C. Columbia
    Columbia is an outdoor apparel and footwear brand known for its durable, weather-resistant gear for activities like hiking, skiing, and camping.
  • D. Columbia
    Columbia was the command module spacecraft of NASA's historic Apollo 11 mission, which carried astronauts to the Moon and safely returned them to Earth in 1969.
  • E. Columbia chosen
    Columbia was NASA’s first operational Space Shuttle orbiter, notable for pioneering reusable spacecraft missions and tragically being lost in the 2003 reentry disaster.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69d889df6dc081908f67dbadc03c07ee completed April 10, 2026, 5:25 a.m.
NER Named-entity recognition batch_69e4545e64448190a2a63bc13f549027 completed April 19, 2026, 4:04 a.m.
Created at: April 10, 2026, 5:49 a.m.