Triple
T33133530
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NROL-44 |
E847937
|
entity |
| Predicate | launchWindow |
P180999
|
FINISHED |
| Object | repeatedly delayed before final launch |
—
|
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: repeatedly delayed before final launch | Statement: [NROL-44, launchWindow, repeatedly delayed before final launch]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: launchWindow Context triple: [NROL-44, launchWindow, repeatedly delayed before final launch]
-
A.
launchAs
Indicates that one entity initiates or starts another entity in a particular role, mode, or form.
-
B.
launcherType
Indicates the specific kind or category of launcher associated with or used in relation to an entity.
-
C.
launchProgram
Indicates initiating the execution of a specified software application or program.
-
D.
launchTitleFor
Indicates that something serves as the title used when launching or presenting another entity (such as an app, feature, or experience).
-
E.
launcherFeature
Indicates that one entity functions as a feature, capability, or component provided by a launcher or launching system for another entity.
- 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_69f3495961d88190b16ea542c2c5f825 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f75dc25fa08190b371faf36d9fb72c |
completed | May 3, 2026, 2:37 p.m. |
| PD | Predicate disambiguation | batch_69f758586534819083e91172f4bf5098 |
completed | May 3, 2026, 2:14 p.m. |
| PDg | Predicate description generation | batch_69f75dc140c4819085063d6c4c36ca61 |
completed | May 3, 2026, 2:37 p.m. |
Created at: May 1, 2026, 1:27 a.m.