Triple
T7743697
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | STS-2 |
E175570
|
entity |
| Predicate | primaryObjectives |
P1415
|
FINISHED |
| Object | test reusable orbiter systems on second flight |
—
|
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: test reusable orbiter systems on second flight | Statement: [STS-2, primaryObjectives, test reusable orbiter systems on second flight]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryObjectives Context triple: [STS-2, primaryObjectives, test reusable orbiter systems on second flight]
-
A.
primaryTarget
Indicates that an entity is the main or most important target of another entity’s action, focus, or effect.
-
B.
primaryMissionTo
Indicates that an entity has a main or principal mission directed toward or focused on another entity.
-
C.
secondaryGoal
Indicates that something serves as a subordinate or supporting objective in addition to a primary goal.
-
D.
initialGoal
Indicates that something represents the first or starting objective or target in a sequence of goals.
-
E.
hasPrimaryGoal
chosen
Indicates that an entity’s main or most important objective is the specified goal.
- 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_69c6995f9c60819092e386192bd63c6f |
completed | March 27, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69c70402169481909b219dc5f4a64b9b |
completed | March 27, 2026, 10:26 p.m. |
| PD | Predicate disambiguation | batch_69c7016c4a748190a7012030edaefcee |
completed | March 27, 2026, 10:15 p.m. |
Created at: March 27, 2026, 4:07 p.m.