Triple
T34714165
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NASA Astronaut Group 20 |
E1000727
|
entity |
| Predicate | selectionPurpose |
P3364
|
FINISHED |
| Object | International Space Station missions |
—
|
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: International Space Station missions | Statement: [NASA Astronaut Group 20, selectionPurpose, International Space Station missions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: selectionPurpose Context triple: [NASA Astronaut Group 20, selectionPurpose, International Space Station missions]
-
A.
selectionReason
chosen
Indicates the reason or justification for choosing or selecting one entity over alternatives.
-
B.
entryPurpose
Indicates the reason or intended use for which an entity is being entered, accessed, or recorded in a given context.
-
C.
purpose
Indicates that one entity exists, is done, or is used in order to achieve, support, or serve the goal, function, or intended outcome of another entity.
-
D.
tagPurpose
Indicates the intended role, function, or use associated with a given tag in a particular context.
-
E.
accessPurpose
Indicates that one entity uses or accesses another entity specifically for a defined purpose or intended use.
- 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_69f76dad3f108190a280fd0a2f4ee89a |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f77ffa6b68819090257fed3802c239 |
completed | May 3, 2026, 5:03 p.m. |
| PD | Predicate disambiguation | batch_69f7795978c481909e152cd1bd02dd07 |
completed | May 3, 2026, 4:35 p.m. |
Created at: May 3, 2026, 3:59 p.m.