Triple
T16585365
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MEV-1 |
E402941
|
entity |
| Predicate | publicHealthResponseDepicted |
P18421
|
FINISHED |
| Object | quarantine measures |
—
|
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: quarantine measures | Statement: [MEV-1, publicHealthResponseDepicted, quarantine measures]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: publicHealthResponseDepicted Context triple: [MEV-1, publicHealthResponseDepicted, quarantine measures]
-
A.
publicHealthResponse
chosen
Indicates actions and measures taken by authorities or organizations to prevent, control, or mitigate health threats within a population.
-
B.
publicHealthDomain
Indicates that something is related to, situated within, or primarily concerned with the field of public health.
-
C.
publicHealthSignificance
Indicates that something has importance, impact, or relevance for the health of the public or population at large.
-
D.
publicHealthReputation
Indicates the perceived standing or esteem of an entity regarding its impact on and responsibility for public health.
-
E.
hasHealthCode
Indicates that an entity is associated with a specific health-related classification or status code.
- 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_69d88387363c8190a97a0c942130de97 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3599b057881909fcb8bbb156633a8 |
completed | April 18, 2026, 10:14 a.m. |
| PD | Predicate disambiguation | batch_69e296a7d9d0819088555bca6c936e79 |
completed | April 17, 2026, 8:23 p.m. |
Created at: April 10, 2026, 5:16 a.m.