Triple
T33081081
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NROL-71 |
E846508
|
entity |
| Predicate | firstLaunchAttemptStatus |
—
|
GENERATED |
| Object | scrubbed |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstLaunchAttemptStatus Context triple: [NROL-71, firstLaunchAttemptStatus, scrubbed]
-
A.
firstLaunchMission
Indicates that a mission is the first launch associated with a particular object, program, or entity.
-
B.
firstTestLaunch
Indicates that an entity’s initial test launch event occurs, marking the first time it is experimentally deployed or sent into operation.
-
C.
firstModuleLaunch
Indicates the event or relationship where the initial module of a system, project, or mission is launched or activated for the first time.
-
D.
secondLaunchOutcome
Indicates the result or status of the entity’s second launch attempt or event.
-
E.
firstRunAt
Indicates the date and time at which an entity was first executed, launched, or run.
- F. None of above. chosen
Provenance (1 batch)
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_69f34954d46c8190a04a159cc5f99efd |
completed | April 30, 2026, 12:21 p.m. |
Created at: May 1, 2026, 1:26 a.m.