Triple
T2139089
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RADARSAT Constellation Mission |
E46719
|
entity |
| Predicate | repeatCycle |
P24840
|
FINISHED |
| Object | 4 days |
—
|
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: 4 days | Statement: [RADARSAT Constellation Mission, repeatCycle, 4 days]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: repeatCycle Context triple: [RADARSAT Constellation Mission, repeatCycle, 4 days]
-
A.
cycleType
Indicates the specific kind or category of cycle involved in a repeated or cyclical process or relationship.
-
B.
followsCycle
Indicates that one entity adheres to or repeats a recurring sequence, pattern, or cycle defined or exemplified by another entity.
-
C.
recentCycle
Indicates that the referenced event, process, or cycle occurred in the most recent iteration or time period relative to the current context.
-
D.
repetitionPattern
chosen
Indicates a recurring structure or sequence in which an action, event, or element is repeated over time or across instances.
-
E.
notableRepeatBy
Indicates that an action, event, or pattern occurs repeatedly and is notably performed, exhibited, or instantiated by a particular 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_69a88a174ab48190a5db20c132e5dccf |
completed | March 4, 2026, 7:37 p.m. |
| NER | Named-entity recognition | batch_69abbf74147c81908793c3694894f94a |
completed | March 7, 2026, 6:02 a.m. |
| PD | Predicate disambiguation | batch_69abbd96a3b0819081efbfef975e1513 |
completed | March 7, 2026, 5:54 a.m. |
Created at: March 4, 2026, 7:44 p.m.