Triple
T31587341
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MediShield Life |
E805989
|
entity |
| Predicate | isLifelong |
P24161
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [MediShield Life, isLifelong, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isLifelong Context triple: [MediShield Life, isLifelong, true]
-
A.
isForLife
chosen
Indicates that something is intended to last or remain valid for the entire duration of a person’s or entity’s life.
-
B.
lifetimeUse
Indicates that the relationship or action concerns the total or cumulative extent of use of something over the entire duration of an entity’s existence or observation period.
-
C.
lifetimeRequirement
Indicates that one entity imposes or must satisfy a specified duration or lifespan condition in relation to another entity or context.
-
D.
hasLifetimeStatus
Indicates that an entity is associated with a status or condition that applies for the entire duration of its existence.
-
E.
isEternal
Indicates that something exists without beginning or end, persisting indefinitely through all time.
- 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_69f348d4891c8190b02bae3c8ecb68b7 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6a80df52c819092af926fd63fa1a3 |
completed | May 3, 2026, 1:42 a.m. |
| PD | Predicate disambiguation | batch_69f6a75656e081908739ed9e2f600e42 |
completed | May 3, 2026, 1:39 a.m. |
Created at: April 30, 2026, 10:26 p.m.