Triple
T20967953
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chen Shui-bian |
E516418
|
entity |
| Predicate | medicalParole |
P81883
|
FINISHED |
| Object | 2015 |
—
|
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: 2015 | Statement: [Chen Shui-bian, medicalParole, 2015]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: medicalParole Context triple: [Chen Shui-bian, medicalParole, 2015]
-
A.
medicalPractice
Indicates a relationship where an entity engages in or carries out the professional provision of medical care or services.
-
B.
eventuallyParoled
chosen
Indicates that an individual who was previously incarcerated was later released from prison on parole.
-
C.
mayBeAdmitted
Indicates that an entity has the possibility or permission to be allowed entry or accepted into another entity or context.
-
D.
medicalAbuseOf
Indicates that one entity subjects another to harmful, exploitative, or unethical treatment within a medical or healthcare context.
-
E.
requiresMedicalClearance
Indicates that one entity must obtain formal approval from a qualified medical authority before engaging in, accessing, or proceeding with the other entity or activity.
- 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_69e0b4fde6c48190af1398e7e734629e |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6fb9d6b548190af7214ad2468cfbf |
completed | April 21, 2026, 4:22 a.m. |
| PD | Predicate disambiguation | batch_69e5dbe6976081908abd4e9c8734bae9 |
completed | April 20, 2026, 7:55 a.m. |
Created at: April 16, 2026, 1:39 p.m.