Triple
T11787307
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | STS-83 |
E280302
|
entity |
| Predicate | orbiter |
P4019
|
FINISHED |
| Object | Columbia |
E221498
|
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: Columbia | Statement: [STS-83, orbiter, Columbia]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Columbia Context triple: [STS-83, orbiter, Columbia]
-
A.
Columbia
Columbia is a small unincorporated community located in the state of Iowa in the United States.
-
B.
Columbia
Columbia is a historic Gold Rush-era town in Tuolumne County, California, preserved today as a state historic park and tourist destination.
-
C.
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.
-
D.
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.
-
E.
Columbia
Columbia is a fictional sentient spaceship, also known as Nuna, featured in science fiction storytelling.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d6ab258b808190b1735835c841e3a4 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8a586803481909af0032c35ca6e51 |
completed | April 10, 2026, 7:23 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f43f8a57ec8190aded70ae89aa8cf7 |
completed | May 1, 2026, 5:52 a.m. |
Created at: April 8, 2026, 9:42 p.m.