Triple
T33133531
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NROL-44 |
E847937
|
entity |
| Predicate | launchOrbitInsertion |
P104167
|
FINISHED |
| Object | geosynchronous transfer 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: geosynchronous transfer orbit | Statement: [NROL-44, launchOrbitInsertion, geosynchronous transfer orbit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: launchOrbitInsertion Context triple: [NROL-44, launchOrbitInsertion, geosynchronous transfer orbit]
-
A.
MarsOrbitInsertion
Indicates the event or process of a spacecraft transitioning into a stable orbit around Mars.
-
B.
orbitInsertionAttempt
Indicates an attempt to place an object into a stable orbit around a celestial body.
-
C.
designedForOrbitInsertion
Indicates that something is intended or configured to perform or facilitate the insertion of an object into orbit.
-
D.
orbitInjectionMethod
chosen
Indicates the method or technique used to insert an object into a specific orbit.
-
E.
launchSpacecraft
Indicates initiating the sending of a spacecraft from a launch site into space, typically by activating and controlling its launch vehicle.
- 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_69f3495961d88190b16ea542c2c5f825 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f760a35b988190904e6267553ad2fe |
completed | May 3, 2026, 2:50 p.m. |
| PD | Predicate disambiguation | batch_69f75eb3d6f081908c933474eb359e3d |
completed | May 3, 2026, 2:41 p.m. |
Created at: May 1, 2026, 1:27 a.m.