Triple
T29056936
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EUMETSAT Polar System |
E735410
|
entity |
| Predicate | frequencyOfRevisit |
P52563
|
FINISHED |
| Object | global coverage several times per day |
—
|
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: global coverage several times per day | Statement: [EUMETSAT Polar System, frequencyOfRevisit, global coverage several times per day]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: frequencyOfRevisit Context triple: [EUMETSAT Polar System, frequencyOfRevisit, global coverage several times per day]
-
A.
visitorFrequency
Indicates how often a visitor comes to or interacts with a particular entity or location.
-
B.
dealFrequency
Indicates how often a particular deal, transaction, or agreement occurs within a given period.
-
C.
frequentlyVisitedBy
Indicates that an entity is regularly or often visited by another entity.
-
D.
hasRevisitTime
chosen
Indicates the interval or schedule at which an entity is revisited, repeated, or observed again.
-
E.
surveyRepetitions
Indicates the number of times a particular survey is administered or repeated within a given context.
- 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_69f077e85498819088b65186550da8cd |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f6617ba4a88190bfc5c305acb4f93f |
completed | May 2, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69f660f082508190a95a7888ad66cb2e |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 28, 2026, 10:12 a.m.