Triple
T36099549
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Charles A. Bassett II |
E1044162
|
entity |
| Predicate | positionOnMission |
P200440
|
FINISHED |
| Object | pilot of Gemini 9 (original assignment) |
—
|
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: pilot of Gemini 9 (original assignment) | Statement: [Charles A. Bassett II, positionOnMission, pilot of Gemini 9 (original assignment)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionOnMission Context triple: [Charles A. Bassett II, positionOnMission, pilot of Gemini 9 (original assignment)]
-
A.
positionInMission
chosen
Indicates the specific role, rank, or placement an entity holds within a particular mission or operation.
-
B.
positionOn
Indicates that one entity is located on top of or at a specific place along the surface or extent of another entity.
-
C.
positionOnTactics
Indicates the stance or viewpoint an entity holds regarding a particular tactic or set of tactics.
-
D.
placeOfMission
Indicates the location where a mission, assignment, or task is carried out or based.
-
E.
positionInPlan
Indicates the specific place or ordering of an element within a larger plan or sequence of planned steps.
- 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_69f76e338e2c8190b7f3bc68bec76349 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69ff956dc6548190979171d4b4068d47 |
completed | May 9, 2026, 8:13 p.m. |
| PD | Predicate disambiguation | batch_69ff93dc39c481908a97a12c3ef7dfe7 |
completed | May 9, 2026, 8:06 p.m. |
Created at: May 3, 2026, 4:08 p.m.