Triple
T6003641
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Emgality |
E133653
|
entity |
| Predicate | halfLife |
P38026
|
FINISHED |
| Object | approximately 27 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: approximately 27 days | Statement: [Emgality, halfLife, approximately 27 days]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: halfLife Context triple: [Emgality, halfLife, approximately 27 days]
-
A.
heldForLife
Indicates that something is possessed, controlled, or held by an entity for the entire duration of that entity’s life, without transfer or expiration before death.
-
B.
hasMeanLifetime
Indicates the characteristic average time duration for which an entity, state, or condition persists before it decays, ends, or changes.
-
C.
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.
-
D.
deathTerritory
Indicates the territory or geographic area where a death occurred or is officially recorded.
-
E.
saidToBeTheLast
Indicates that something or someone is claimed or reported to be the final instance or member in a sequence, series, or group.
- 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_69c00872444c8190bfaf1739dcec765c |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c04f0f63148190826198281dce3713 |
completed | March 22, 2026, 8:20 p.m. |
| PD | Predicate disambiguation | batch_69c049e3316c819087ea635fa7ee8472 |
completed | March 22, 2026, 7:58 p.m. |
Created at: March 22, 2026, 4:06 p.m.