Triple
T28711430
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Meteosat Second Generation |
E729840
|
entity |
| Predicate | imageRepeatCycle |
P24840
|
FINISHED |
| Object | 15 minutes |
—
|
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: 15 minutes | Statement: [Meteosat Second Generation, imageRepeatCycle, 15 minutes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: imageRepeatCycle Context triple: [Meteosat Second Generation, imageRepeatCycle, 15 minutes]
-
A.
repetitionPattern
chosen
Indicates a recurring structure or sequence in which an action, event, or element is repeated over time or across instances.
-
B.
repetitionCount
Indicates the number of times a particular event, action, or pattern is repeated within a given context.
-
C.
iconographicCycle
Indicates a relationship where multiple visual representations are linked together as parts of a coherent, sequential iconographic narrative or thematic series.
-
D.
frescoCycleBy
Indicates that one fresco belongs to, or is part of, a larger thematic or narrative cycle of frescoes.
-
E.
repetitionOf
Indicates that one entity is a repeated occurrence or instance of another entity, preserving the same content or pattern.
- 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_69f043e7d5a4819094b18aca10b1e024 |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69f6645ba71c81908044ade6ab577018 |
completed | May 2, 2026, 8:53 p.m. |
| PD | Predicate disambiguation | batch_69f663362c008190a22afed262f1e426 |
completed | May 2, 2026, 8:48 p.m. |
Created at: April 28, 2026, 5:48 a.m.