Triple
T7780395
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Columbia |
E221498
|
entity |
| Predicate | lastMissionType |
P22637
|
FINISHED |
| Object | microgravity research mission |
—
|
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: microgravity research mission | Statement: [Columbia, lastMissionType, microgravity research mission]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lastMissionType Context triple: [Columbia, lastMissionType, microgravity research mission]
-
A.
typeOfMission
chosen
Indicates the specific category or nature of a mission that an entity is associated with or engaged in.
-
B.
finalMissionOf
Indicates that one entity is the last mission, assignment, or operation undertaken by another entity.
-
C.
lastMP
Indicates that one entity is the most recent Member of Parliament (MP) associated with, representing, or holding office for the other entity.
-
D.
nextMission
Indicates that one mission directly follows another in a planned or chronological sequence.
-
E.
overseesMissionType
Indicates that one entity has responsibility for supervising or managing a particular type or category of mission carried out by another 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_69ca83ebbef881909ac47f789145fef7 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cae7e779ec8190b77296d9c2ac3210 |
completed | March 30, 2026, 9:15 p.m. |
| PD | Predicate disambiguation | batch_69caa488532c819093ac40bba0b3c7ef |
completed | March 30, 2026, 4:27 p.m. |
Created at: March 30, 2026, 4:20 p.m.