Triple
T6015208
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | STS-43 |
E133932
|
entity |
| Predicate | tdrsOrbit |
P7214
|
FINISHED |
| Object | geosynchronous transfer orbit deployment |
—
|
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: geosynchronous transfer orbit deployment | Statement: [STS-43, tdrsOrbit, geosynchronous transfer orbit deployment]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tdrsOrbit Context triple: [STS-43, tdrsOrbit, geosynchronous transfer orbit deployment]
-
A.
orbitType
chosen
Indicates the specific kind or classification of an object's orbit in relation to the body it revolves around.
-
B.
orbiterStatus
Indicates the current operational or mission state of an orbiting spacecraft relative to its target body or mission phase.
-
C.
orbiterNumber
Indicates the identifying number assigned to a specific orbiter associated with an object or mission.
-
D.
orbiterDesignation
Indicates that one entity is designated as an orbiter (spacecraft or object in orbit) associated with another entity.
-
E.
orbitReference
Indicates that one entity serves as the orbital frame, path, or reference system relative to which another entity’s orbit is defined or described.
- 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_69c0087361a48190905c6b55969852b8 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c04f80ec108190ae9711727debb061 |
completed | March 22, 2026, 8:22 p.m. |
| PD | Predicate disambiguation | batch_69c049e75b3881908be106fbcf8c68d4 |
completed | March 22, 2026, 7:58 p.m. |
Created at: March 22, 2026, 4:06 p.m.