Triple
T33081105
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NROL-71 |
E846508
|
entity |
| Predicate | hasLaunchPatch |
P198199
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [NROL-71, hasLaunchPatch, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLaunchPatch Context triple: [NROL-71, hasLaunchPatch, yes]
-
A.
hasLaunch
Indicates that an entity initiates or carries out the launch of another entity (such as a product, mission, or event).
-
B.
hasLaunchRange
Indicates that one entity (typically a weapon or vehicle) has the capability to be launched or to operate effectively within a specified distance range from a target or origin.
-
C.
hasLaunchContext
Indicates that an entity is associated with a specific situation, environment, or set of conditions under which it is initiated or launched.
-
D.
launchedWith
Indicates that one entity was initiated, started, or set into motion together with another entity as part of the same launch event.
-
E.
introducedInPatch
Indicates that something (such as a feature, change, or fix) first appeared or became available in a specific software patch.
- 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_69fed09a12648190affcd9bacf7ca275 |
completed | May 9, 2026, 6:13 a.m. |
| PD | Predicate disambiguation | batch_69fecf91d6f481908deb60c965c433ed |
completed | May 9, 2026, 6:09 a.m. |
| PDg | Predicate description generation | batch_69fed098328c819085979de6b179b378 |
completed | May 9, 2026, 6:13 a.m. |
Created at: May 1, 2026, 1:26 a.m.