Triple
T31587330
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MediShield Life |
E805989
|
entity |
| Predicate | isCompulsory |
P76724
|
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, isCompulsory, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isCompulsory Context triple: [MediShield Life, isCompulsory, true]
-
A.
isObligatory
chosen
Indicates that an entity is required or must be performed, fulfilled, or complied with according to some rule, norm, or obligation.
-
B.
compulsoryEnrollment
Indicates that participation or registration in a specified program, course, or institution is required by rule or law rather than left to individual choice.
-
C.
isMandatoryFor
Indicates that something is required or compulsory for another thing to occur, be valid, or be completed.
-
D.
compulsoryEducation
Indicates that an entity is legally required to participate in a specified level or period of formal education.
-
E.
isMandatoryInSomeJurisdictions
Indicates that the subject is legally required or compulsory in at least one jurisdiction or legal authority.
- 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_69f6df450014819099d118e5c2d697fa |
completed | May 3, 2026, 5:38 a.m. |
| PD | Predicate disambiguation | batch_69f6de07836481908785cde9c511920b |
completed | May 3, 2026, 5:32 a.m. |
Created at: April 30, 2026, 10:26 p.m.