Triple

T32524123
Position Surface form Disambiguated ID Type / Status
Subject COVID-19 pandemic in Belgium E831261 entity
Predicate dataReportingBody P113487 FINISHED
Object Sciensano daily COVID-19 reports 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: Sciensano daily COVID-19 reports | Statement: [COVID-19 pandemic in Belgium, dataReportingBody, Sciensano daily COVID-19 reports]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: dataReportingBody
Context triple: [COVID-19 pandemic in Belgium, dataReportingBody, Sciensano daily COVID-19 reports]
  • A. reportingBody
    Indicates the entity that is responsible for providing or submitting a report about another entity or event.
  • B. dataReportedBy chosen
    Indicates that certain data has been provided, recorded, or communicated by a specific source or reporting entity.
  • C. dataReportedAs
    Indicates that specific information has been communicated or recorded in a particular stated form, value, or representation.
  • D. reportsFor
    Indicates that one entity is subordinate to another and is required to provide updates or answer to that entity, typically within an organizational or hierarchical structure.
  • E. regulatoryReporting
    Indicates the relationship where one party prepares and submits required information or disclosures to a regulatory authority in order to comply with legal or supervisory reporting obligations.
  • 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_69f34923e1548190be0524205d8cdf8f completed April 30, 2026, 12:20 p.m.
NER Named-entity recognition batch_69f6c516640c81909fce8dc8240a00a9 completed May 3, 2026, 3:46 a.m.
PD Predicate disambiguation batch_69f6bd2a14b081908162923dfbf0a6f4 completed May 3, 2026, 3:12 a.m.
Created at: May 1, 2026, 1:01 a.m.