Triple
T11466975
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CDC Category A agent |
E271803
|
entity |
| Predicate | hasPriorityLevel |
P2393
|
FINISHED |
| Object | highest priority |
—
|
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: highest priority | Statement: [CDC Category A agent, hasPriorityLevel, highest priority]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPriorityLevel Context triple: [CDC Category A agent, hasPriorityLevel, highest priority]
-
A.
hasPriorityAt
Indicates that one entity holds a specified level of priority or precedence at a particular time, place, or context relative to others.
-
B.
hasLevel
chosen
Indicates that an entity possesses or is associated with a particular degree, rank, or stage within an ordered scale or hierarchy.
-
C.
hasPriorityGroup
Indicates that one entity is assigned to, or associated with, a specific priority group relative to others.
-
D.
hasPriorityIssue
Indicates that an entity is associated with an issue that is marked as high or urgent priority.
-
E.
hasGovernancePriority
Indicates that a particular issue, objective, or domain is assigned a specified level of importance or precedence within a governance framework or decision-making process.
- 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_69d6aae0c8d881908a5a360c0be3242e |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d822f5eb988190b309b8e309f6d1a5 |
completed | April 9, 2026, 10:06 p.m. |
| PD | Predicate disambiguation | batch_69d80867ff248190bb157fa9e355353b |
completed | April 9, 2026, 8:13 p.m. |
Created at: April 8, 2026, 9:35 p.m.