Triple
T28067309
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Starship spacecraft |
E709289
|
entity |
| Predicate | selectedForProgram |
P10044
|
FINISHED |
| Object | NASA Artemis program |
—
|
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: NASA Artemis program | Statement: [Starship spacecraft, selectedForProgram, NASA Artemis program]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: selectedForProgram Context triple: [Starship spacecraft, selectedForProgram, NASA Artemis program]
-
A.
selectedAt
Indicates that an entity was chosen or picked at a specific point in time or under particular selection conditions.
-
B.
selectedTo
chosen
Indicates that one entity has been chosen or designated from a set of candidates to perform a role, receive something, or participate in an activity in relation to another entity.
-
C.
subjectToProgram
Indicates that an entity is governed, regulated, or affected by a specific program, policy, or systematic initiative.
-
D.
selectedWith
Indicates that one entity is chosen or picked in conjunction with, or as part of a set including, another entity.
-
E.
coordinatesProgramsOf
Indicates that one entity organizes and manages the activities or operations of another entity’s programs to ensure they function in a unified and efficient manner.
- 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_69ef9b6eb6d88190a3fea236eb0f7bed |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69f6645ba71c81908044ade6ab577018 |
completed | May 2, 2026, 8:53 p.m. |
| PD | Predicate disambiguation | batch_69f663362c008190a22afed262f1e426 |
completed | May 2, 2026, 8:48 p.m. |
Created at: April 27, 2026, 8:43 p.m.