Triple
T4784994
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | mAb114 |
E106453
|
entity |
| Predicate | administrationRegimen |
P37228
|
FINISHED |
| Object | single-dose intravenous infusion |
—
|
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-dose intravenous infusion | Statement: [mAb114, administrationRegimen, single-dose intravenous infusion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: administrationRegimen Context triple: [mAb114, administrationRegimen, single-dose intravenous infusion]
-
A.
doseRegimen
chosen
Indicates the specific schedule, frequency, and amount with which a dose of a substance or medication is to be administered.
-
B.
hasDosingRegimen
Indicates that an entity is associated with a specific dosing regimen, defining how and when a dose is to be administered.
-
C.
typeOfAdministration
Indicates the specific form or system of administration applied to or governing an entity.
-
D.
administeredWith
Indicates that two or more treatments, drugs, or interventions are given to a patient at the same time or as part of the same therapeutic regimen.
-
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_69bd43f4a9588190bf73e20bc27c03cc |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd65ae49ec81908f16248d22d1155f |
completed | March 20, 2026, 3:20 p.m. |
| PD | Predicate disambiguation | batch_69bd622e1b408190806c15c61519fc74 |
completed | March 20, 2026, 3:05 p.m. |
Created at: March 20, 2026, 1:22 p.m.