Triple
T3864865
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ATV spacecraft |
E91826
|
entity |
| Predicate | reboostCapability |
P51548
|
FINISHED |
| Object | ISS orbit raising |
—
|
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: ISS orbit raising | Statement: [ATV spacecraft, reboostCapability, ISS orbit raising]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reboostCapability Context triple: [ATV spacecraft, reboostCapability, ISS orbit raising]
-
A.
restartCapability
Indicates the ability or permission for an entity to be restarted, typically after a stop, failure, or configuration change.
-
B.
boosterRecoveryMethod
Indicates the method or process used to recover a rocket booster after its mission.
-
C.
usedCapability
Indicates that an entity employed or exercised a particular capability, skill, or function in performing an action or achieving a result.
-
D.
returnCapability
Indicates the ability or provision for something to be sent, given, or transferred back to its original sender, owner, or source.
-
E.
recoveryCapability
Indicates the ability of an entity to return to a normal or functional state after experiencing damage, failure, or disruption.
- F. None of above. chosen
Provenance (4 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_69aed9645f348190a9868e7cef56ab7e |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aeec3a253c81909df7dc0422ff7989 |
completed | March 9, 2026, 3:50 p.m. |
| PD | Predicate disambiguation | batch_69aee754dddc8190936e1f9c40a770db |
completed | March 9, 2026, 3:29 p.m. |
| PDg | Predicate description generation | batch_69aee80858a481909961a33fb50ff8d1 |
completed | March 9, 2026, 3:32 p.m. |
Created at: March 9, 2026, 3:19 p.m.