Triple
T31628771
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Codogno |
E807099
|
entity |
| Predicate | COVID-19ContainmentZone |
P162399
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Codogno, COVID-19ContainmentZone, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: COVID-19ContainmentZone Context triple: [Codogno, COVID-19ContainmentZone, yes]
-
A.
hasCOVID19Restriction
Indicates that some form of COVID-19–related rule, limitation, or special condition applies to the referenced entity or activity.
-
B.
wasCOVID19Hotspot
chosen
Indicates that a location or entity experienced a particularly high concentration or rate of COVID-19 cases during a specific period.
-
C.
hasEmergencyPlanningZone
Indicates that an entity is associated with a designated emergency planning zone within which specific preparedness and response measures apply.
-
D.
wasQuarantineStationFor
Indicates that a location served as a designated quarantine facility for a particular group of people, animals, or goods.
-
E.
epidemicControlActivities
Indicates actions or measures undertaken to prevent, contain, or mitigate the spread and impact of an epidemic.
- 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_69f348d7883c8190b6c13ab92b7ef076 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6abaa1f648190b77073771df3bf3b |
completed | May 3, 2026, 1:58 a.m. |
| PD | Predicate disambiguation | batch_69f6aa1e84b88190b025f6ca40f17a8a |
completed | May 3, 2026, 1:51 a.m. |
Created at: April 30, 2026, 10:44 p.m.