Triple
T33081081
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NROL-71 |
E846508
|
entity |
| Predicate | firstLaunchAttemptStatus |
P206342
|
FINISHED |
| Object | scrubbed |
—
|
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: scrubbed | Statement: [NROL-71, firstLaunchAttemptStatus, scrubbed]
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 (4 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_69f34954d46c8190a04a159cc5f99efd |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a037c9141dc819098d7fcc36e69882c |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379f338b881908e5593e45d764f4d |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c7fb9f88190b384b1b68200aef0 |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 1, 2026, 1:26 a.m.