Triple
T8627819
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | JPSS-4 |
E204321
|
entity |
| Predicate | belongsToProgramPhase |
P22825
|
FINISHED |
| Object | post-NOAA-20 JPSS satellites |
—
|
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: post-NOAA-20 JPSS satellites | Statement: [JPSS-4, belongsToProgramPhase, post-NOAA-20 JPSS satellites]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: belongsToProgramPhase Context triple: [JPSS-4, belongsToProgramPhase, post-NOAA-20 JPSS satellites]
-
A.
belongsToProgram
Indicates that an entity is a member of, or is associated with, a specific program.
-
B.
hasPhaseRelation
Indicates that two entities are related by a specific phase difference or phase alignment in time or a cyclical process.
-
C.
programPhase
chosen
Indicates the specific stage or phase within a broader program or process that an entity is currently associated with.
-
D.
appliesToPhase
Indicates that a particular rule, condition, or action is relevant to and operates during a specific phase within a process or lifecycle.
-
E.
targetsPhase
Indicates that an action, process, or entity is specifically directed toward or intended to affect a particular phase or stage within a larger sequence or lifecycle.
- 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_69ca834a4ea0819094970dceb9e389f3 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5730309081909a9a0256c9bf5f8f |
completed | March 31, 2026, 11:22 p.m. |
| PD | Predicate disambiguation | batch_69cc455906f8819082edd79cb4a1cf28 |
completed | March 31, 2026, 10:06 p.m. |
Created at: March 30, 2026, 6:27 p.m.