Triple
T15555544
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | STS-49 |
E370856
|
entity |
| Predicate | evaObjective |
P30831
|
FINISHED |
| Object | capture Intelsat VI F-3 using capture bar |
—
|
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: capture Intelsat VI F-3 using capture bar | Statement: [STS-49, evaObjective, capture Intelsat VI F-3 using capture bar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: evaObjective Context triple: [STS-49, evaObjective, capture Intelsat VI F-3 using capture bar]
-
A.
EVAobjective
chosen
Indicates that an extravehicular activity (EVA) is performed with the purpose of achieving a specific objective or goal.
-
B.
usesObjective
Indicates that an agent employs or applies a particular object, tool, or resource to carry out an action or achieve a goal.
-
C.
opponentObjective
Indicates that one entity is the target or goal that an opposing entity aims to counter, defeat, or prevent from succeeding.
-
D.
gameObjective
Indicates the primary goal or intended outcome that participants aim to achieve within a game.
-
E.
trainingObjective
Indicates the goal or target outcome that a training process is designed to achieve.
- 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_69d85cc6cf40819091f4a5facee1ebe6 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04a97dbfc8190a98cbbac5e71ba88 |
completed | April 16, 2026, 2:34 a.m. |
| PD | Predicate disambiguation | batch_69deda7e6e748190b29ccce23298afef |
completed | April 15, 2026, 12:23 a.m. |
Created at: April 10, 2026, 4:09 a.m.