Triple
T33388958
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zabdeno |
E854993
|
entity |
| Predicate | isPartOfRegimenWith |
P37862
|
FINISHED |
| Object | Mvabea |
—
|
NE NERFINISHED |
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: Mvabea | Statement: [Zabdeno, isPartOfRegimenWith, Mvabea]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPartOfRegimenWith Context triple: [Zabdeno, isPartOfRegimenWith, Mvabea]
-
A.
hasDosingRegimen
Indicates that an entity is associated with a specific dosing regimen, defining how and when a dose is to be administered.
-
B.
belongsToRegimen
chosen
Indicates that something is a component or member of a specified regimen or structured treatment plan.
-
C.
controlRegimen
Indicates that an entity is responsible for directing, managing, or governing a particular regimen, protocol, or set of prescribed procedures.
-
D.
regimenDependsOn
Indicates that the applicability or outcome of a regimen is contingent upon another specified factor, condition, or regimen.
-
E.
doseRegimen
Indicates the specific schedule, frequency, and amount with which a dose of a substance or medication is to be administered.
- 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_69f3496d54048190a1cb91fdd7caa6ea |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69ff16775a9881909d26dbc1f0ef3e1c |
completed | May 9, 2026, 11:11 a.m. |
| PD | Predicate disambiguation | batch_69ff158e61708190a1c581d0d306cfce |
completed | May 9, 2026, 11:07 a.m. |
Created at: May 1, 2026, 1:35 a.m.