Triple
T32196383
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | avelumab |
E822413
|
entity |
| Predicate | hasHalfLifeApprox |
P38026
|
FINISHED |
| Object | 6 days to 7 days |
—
|
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: 6 days to 7 days | Statement: [avelumab, hasHalfLifeApprox, 6 days to 7 days]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHalfLifeApprox Context triple: [avelumab, hasHalfLifeApprox, 6 days to 7 days]
-
A.
hasEliminationHalfLife
chosen
Indicates the duration required for half of a substance or entity to be removed, degraded, or rendered inactive within a given system or context.
-
B.
hasMeanLifetime
Indicates the characteristic average time duration for which an entity, state, or condition persists before it decays, ends, or changes.
-
C.
mostStableIsotopeHalfLife
Indicates the duration of time it takes for half of the atoms in the most stable isotope of an element to decay.
-
D.
isInHalf
Indicates that one entity is located within or belongs to a specified half or subdivision of another entity.
-
E.
hasTypicalUseTime
Indicates the usual or expected duration or time period during which something is commonly used or in operation.
- 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_69f349093174819086e633c190a51aa8 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6f38159d08190980ad639e08f00f4 |
completed | May 3, 2026, 7:04 a.m. |
| PD | Predicate disambiguation | batch_69f6e3d7bee48190b94e0beb48a1d7fa |
completed | May 3, 2026, 5:57 a.m. |
Created at: May 1, 2026, 12:36 a.m.