Triple
T10292383
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ad26.COV2.S |
E241393
|
entity |
| Predicate | WHOStatus |
P37233
|
FINISHED |
| Object | Emergency Use Listing granted |
—
|
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: Emergency Use Listing granted | Statement: [Ad26.COV2.S, WHOStatus, Emergency Use Listing granted]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: WHOStatus Context triple: [Ad26.COV2.S, WHOStatus, Emergency Use Listing granted]
-
A.
ICSStatus
Indicates the current state or condition of an entity within an Incident Command System (ICS) context.
-
B.
GIStatusCountry
Indicates the status or condition of a geographic indication (GI) within a specific country.
-
C.
hostNationStatus
Indicates that an entity holds the official status of being the host nation for a particular event, activity, or arrangement.
-
D.
worldHealthOrganizationStatus
chosen
Indicates the relationship between an entity and its classification or status as defined by the World Health Organization (WHO), such as recognition, designation, or official standing.
-
E.
globalStatus
Indicates the overall state or condition of an entity as evaluated at a system-wide or global level.
- 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_69d381aaafc08190af475ef58dc16aba |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4d2d35f048190a215493acdf1f718 |
completed | April 7, 2026, 9:48 a.m. |
| PD | Predicate disambiguation | batch_69d4d1f35e548190be3b4d92d65d2d20 |
completed | April 7, 2026, 9:44 a.m. |
Created at: April 6, 2026, 11:42 a.m.