Triple
T33146357
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NROL-68 |
E848309
|
entity |
| Predicate | launchAnnouncementAgency |
P147438
|
FINISHED |
| Object | United States Space Force |
—
|
NE NERFINISHED |
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: United States Space Force | Statement: [NROL-68, launchAnnouncementAgency, United States Space Force]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: launchAnnouncementAgency Context triple: [NROL-68, launchAnnouncementAgency, United States Space Force]
-
A.
launchAuthority
Indicates the entity that has the official power or responsibility to initiate or authorize the start of an operation, project, or event.
-
B.
launchEntity
Indicates initiating the start, deployment, or release of an entity into operation or into a new state or environment.
-
C.
announcementLocation
Indicates the place or venue where an announcement is made or presented.
-
D.
policyAnnouncedBy
Indicates that a specific policy was publicly communicated or declared by a particular entity (such as a person, organization, or institution).
-
E.
announcementMadeBy
chosen
Indicates that a particular announcement is issued or created by a specific entity (such as a person, organization, or system).
- 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_69f3495a458c8190a1d34b237ba0be3f |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f7626667f48190ad90867eb67ec582 |
completed | May 3, 2026, 2:57 p.m. |
| PD | Predicate disambiguation | batch_69f76175d6608190b60b268e20f49ed9 |
completed | May 3, 2026, 2:53 p.m. |
Created at: May 1, 2026, 1:28 a.m.