Triple
T35984742
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Charles Bassett |
E1040678
|
entity |
| Predicate | missionAssignment |
P146826
|
FINISHED |
| Object | Gemini 9 prime crew |
—
|
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: Gemini 9 prime crew | Statement: [Charles Bassett, missionAssignment, Gemini 9 prime crew]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: missionAssignment Context triple: [Charles Bassett, missionAssignment, Gemini 9 prime crew]
-
A.
assignedMission
chosen
Indicates that an entity has been given a specific mission or task to carry out.
-
B.
missionOrder
Indicates that one mission is ordered, sequenced, or prioritized relative to another within an overall mission plan.
-
C.
commandedMission
Indicates that one entity served as the commanding leader or officer in charge of a particular mission carried out by another entity.
-
D.
questAssigned
Indicates that a quest has been given by one entity to another, establishing an assignment relationship between them.
-
E.
missionAssociation
Indicates a relationship where an entity is connected to, involved in, or associated with a particular mission or organized endeavor.
- 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_69f76e28293c8190ae3f4e2208b87117 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fba2877b248190a974eb092243c0c4 |
completed | May 6, 2026, 8:20 p.m. |
| PD | Predicate disambiguation | batch_69fb8d06a1b48190a937aa410d159dfa |
completed | May 6, 2026, 6:48 p.m. |
Created at: May 3, 2026, 4:07 p.m.