Triple
T27425998
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Heinsberg |
E690485
|
entity |
| Predicate | wasCOVID19Hotspot |
P162399
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Heinsberg, wasCOVID19Hotspot, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasCOVID19Hotspot Context triple: [Heinsberg, wasCOVID19Hotspot, true]
-
A.
wasQuarantineStationFor
Indicates that a location served as a designated quarantine facility for a particular group of people, animals, or goods.
-
B.
hasCOVID19Restriction
Indicates that some form of COVID-19–related rule, limitation, or special condition applies to the referenced entity or activity.
-
C.
epidemicStartInArea
Indicates the point in time and place at which an epidemic begins within a specific geographic area.
-
D.
isReservoirOf
Indicates that one entity serves as a storage source or container holding a particular substance, resource, or quantity for another entity or purpose.
-
E.
officiallyConfirmedIn
Indicates that something has been formally acknowledged or validated within an official document, statement, or process.
- F. None of above. chosen
Provenance (4 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_69ef52003fb48190b0f1295246182a86 |
completed | April 27, 2026, 12:09 p.m. |
| NER | Named-entity recognition | batch_69f62d546b2881909d0acb99ce291de1 |
completed | May 2, 2026, 4:59 p.m. |
| PD | Predicate disambiguation | batch_69f623aaf40081909f947431424a1d55 |
completed | May 2, 2026, 4:17 p.m. |
| PDg | Predicate description generation | batch_69f624c006788190a2f4d5015c96463f |
completed | May 2, 2026, 4:22 p.m. |
Created at: April 27, 2026, 12:40 p.m.