Triple
T6431756
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Antares launch vehicle |
E129793
|
entity |
| Predicate | payloadDestination |
P57570
|
FINISHED |
| Object | low Earth orbit |
—
|
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: low Earth orbit | Statement: [Antares launch vehicle, payloadDestination, low Earth orbit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: payloadDestination Context triple: [Antares launch vehicle, payloadDestination, low Earth orbit]
-
A.
sentToDestination
Indicates that something or someone is transferred or dispatched from an origin to a specified destination.
-
B.
payloadType
Indicates the kind or category of payload associated with or carried by an entity or action.
-
C.
transferDestination
chosen
Indicates the entity that serves as the receiving end or target location of a transfer from another entity.
-
D.
originalDestination
Indicates the initial or intended destination associated with an entity before any changes, rerouting, or redirection occur.
-
E.
attemptedDestination
Indicates that an entity made an effort to reach or go to a particular destination, regardless of whether the attempt was successful.
- 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_69c0084caac48190a7bc2ad8ba44536f |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c0693cadf08190aca84888a3440b3d |
completed | March 22, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69c060f780b08190aa650b4d1fc51f21 |
completed | March 22, 2026, 9:36 p.m. |
Created at: March 22, 2026, 4:44 p.m.