Triple
T14594073
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Member of the Knesset |
E342513
|
entity |
| Predicate | immunityType |
P114976
|
FINISHED |
| Object | parliamentary immunity |
—
|
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: parliamentary immunity | Statement: [Member of the Knesset, immunityType, parliamentary immunity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: immunityType Context triple: [Member of the Knesset, immunityType, parliamentary immunity]
-
A.
immunity
Indicates that an entity is protected against or not affected by a particular agent, condition, or influence.
-
B.
immuneResponseType
Indicates the specific kind or category of immune reaction that occurs in response to a particular stimulus or agent.
-
C.
preExistingImmunityInHumans
Indicates that humans already possess some level of immune protection against a particular agent, condition, or exposure prior to a specified event or intervention.
-
D.
hasRoleInImmunity
Indicates that an entity functions in or contributes to an immune-related process or mechanism.
-
E.
antibodyType
Indicates the specific class or subtype of an antibody involved in the described relationship or context.
- F. None of above. chosen
Provenance (4 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_69d822ddc0f081909cd8163c7de298cd |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb43480d8819084a707e56da2c237 |
completed | April 14, 2026, 9:40 p.m. |
| PD | Predicate disambiguation | batch_69de656a953481909a4645b004c40de7 |
completed | April 14, 2026, 4:03 p.m. |
| PDg | Predicate description generation | batch_69de716c17cc8190aeb85296abee85a7 |
completed | April 14, 2026, 4:55 p.m. |
Created at: April 10, 2026, 1:24 a.m.