Triple
T27343457
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Discovery (OV-103) |
E684169
|
entity |
| Predicate | precededByOrbiter |
P30970
|
FINISHED |
| Object | Columbia (OV-102) |
—
|
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 (OV-102) | Statement: [Discovery (OV-103), precededByOrbiter, Columbia (OV-102)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: precededByOrbiter Context triple: [Discovery (OV-103), precededByOrbiter, Columbia (OV-102)]
-
A.
previousMissionOfOrbiter
chosen
Indicates that one mission is the immediately preceding mission undertaken by a given orbiter.
-
B.
reusedOrbiter
Indicates that the same orbiter spacecraft is used again in a subsequent mission or operation.
-
C.
otherOrbiterName
Indicates that one orbiter is identified or referred to by an alternative or secondary name.
-
D.
locatedInOrbitAbove
Indicates that one entity is positioned in an orbital path around and above another entity.
-
E.
isThirdOrbiter
Indicates that an entity serves as the third object or body orbiting around a specified central entity.
- 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_69ef1480a76481908684256ddd5bfda3 |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69f69edbb7648190bd89c57e0932eac1 |
completed | May 3, 2026, 1:03 a.m. |
| PD | Predicate disambiguation | batch_69f69d17e8d48190b30bcc2f4bd81eb2 |
completed | May 3, 2026, 12:55 a.m. |
Created at: April 27, 2026, 11:44 a.m.