Triple
T10292391
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ad26.COV2.S |
E241393
|
entity |
| Predicate | EMAStatus |
P92939
|
FINISHED |
| Object | Conditional marketing authorization 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: Conditional marketing authorization granted | Statement: [Ad26.COV2.S, EMAStatus, Conditional marketing authorization granted]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: EMAStatus Context triple: [Ad26.COV2.S, EMAStatus, Conditional marketing authorization granted]
-
A.
maintenanceStatus
Indicates the current state or condition of an entity with respect to its maintenance activities, such as whether it is pending, in progress, completed, or overdue.
-
B.
hasEquipmentStatus
Indicates the current operational or condition state assigned to a piece of equipment.
-
C.
operatorStatus
Indicates the current operational state or condition of an operator (e.g., active, inactive, or in error).
-
D.
statusModel
Indicates that an entity is associated with a particular status representation or status-handling model.
-
E.
emblemStatus
Indicates the current state or condition of an emblem, such as whether it is active, valid, displayed, or in use.
- 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_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. |
| PDg | Predicate description generation | batch_69d4d29d7cf08190acd70cee634c5cdb |
completed | April 7, 2026, 9:47 a.m. |
Created at: April 6, 2026, 11:42 a.m.