Triple
T29742985
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NOAA-15 |
E752663
|
entity |
| Predicate | preLaunchDesignation |
P12577
|
FINISHED |
| Object | NOAA-K |
—
|
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: NOAA-K | Statement: [NOAA-15, preLaunchDesignation, NOAA-K]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: preLaunchDesignation Context triple: [NOAA-15, preLaunchDesignation, NOAA-K]
-
A.
preLaunchName
chosen
Indicates the name assigned to something before its official or public launch.
-
B.
preTOPSDesignation
Indicates that an entity has been assigned a preliminary or provisional TOPS (Total Operations Processing System) designation within a classification or tracking system.
-
C.
initiallyDesignated
Indicates that an entity was assigned or specified in a particular role, state, or configuration at the beginning of a process or time period.
-
D.
missionDesignationPrefix
Indicates the standardized prefix string used to label or identify a mission within a naming or designation system.
-
E.
alternateDesignation
Indicates that one entity serves as an alternative name, label, or identifier for another entity.
- 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_69f0d62b064081908c1ae61cd68fb139 |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f673645c888190bdffeb6448487ec4 |
completed | May 2, 2026, 9:57 p.m. |
| PD | Predicate disambiguation | batch_69f66ac1a4fc81909740d2e52fbe6970 |
completed | May 2, 2026, 9:21 p.m. |
Created at: April 28, 2026, 7:49 p.m.