Triple
T10292412
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ad26.COV2.S |
E241393
|
entity |
| Predicate | regimenType |
P24598
|
FINISHED |
| Object | single primary dose with optional booster |
—
|
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: single primary dose with optional booster | Statement: [Ad26.COV2.S, regimenType, single primary dose with optional booster]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regimenType Context triple: [Ad26.COV2.S, regimenType, single primary dose with optional booster]
-
A.
regimenDependsOn
Indicates that the applicability or outcome of a regimen is contingent upon another specified factor, condition, or regimen.
-
B.
doseRegimen
Indicates the specific schedule, frequency, and amount with which a dose of a substance or medication is to be administered.
-
C.
hasDosingRegimen
Indicates that an entity is associated with a specific dosing regimen, defining how and when a dose is to be administered.
-
D.
belongsToRegimenType
chosen
Indicates that something is associated with or classified under a specific regimen type.
-
E.
belongsToRegimen
Indicates that something is a component or member of a specified regimen or structured treatment plan.
- 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.