Triple
T3064251
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Block 1 |
E62064
|
entity |
| Predicate | designedPayloadDestination |
P2066
|
FINISHED |
| Object | lunar 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: lunar orbit | Statement: [Block 1, designedPayloadDestination, lunar orbit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designedPayloadDestination Context triple: [Block 1, designedPayloadDestination, lunar orbit]
-
A.
plannedPayload
Indicates that an entity is designated or scheduled to be carried, delivered, or transported as part of a planned operation or mission.
-
B.
designedPayloadToLEO
Indicates that an object (typically a launch vehicle or system) is designed to deliver a specified payload mass to Low Earth Orbit (LEO).
-
C.
attemptedDestination
Indicates that an entity made an effort to reach or go to a particular destination, regardless of whether the attempt was successful.
-
D.
isDestinationFor
chosen
Indicates that one entity serves as the endpoint or target location that another entity is intended to reach or be directed toward.
-
E.
originalDestination
Indicates the initial or intended destination associated with an entity before any changes, rerouting, or redirection occur.
- 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_69ad85793e5c8190a358049bc4a98d8c |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ad9ea2154c8190ab243feb77170a15 |
completed | March 8, 2026, 4:06 p.m. |
| PD | Predicate disambiguation | batch_69ad9624b7a0819091d255614f5819ea |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 3:02 p.m.