Triple
T34242431
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 19th Knesset |
E878501
|
entity |
| Predicate | enactedLawsFor |
P55287
|
FINISHED |
| Object | State of Israel |
—
|
NE NERFINISHED |
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: State of Israel | Statement: [19th Knesset, enactedLawsFor, State of Israel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: enactedLawsFor Context triple: [19th Knesset, enactedLawsFor, State of Israel]
-
A.
enactedFor
Indicates that an action, rule, or measure is formally established or put into effect on behalf of, or for the benefit of, a particular entity or group.
-
B.
enactedAs
Indicates that one entity has been formally established, implemented, or made legally effective in the specific form represented by another entity.
-
C.
enactedWith
Indicates that an action, law, or policy was formally established or brought into effect through the involvement or authority of a specified agent or instrument.
-
D.
legislativeActOf
Indicates a relationship where a legislative act is authored, enacted, or formally issued by a specific legislative body or authority.
-
E.
promulgatesLawsAt
chosen
Indicates the action by which an authority formally enacts or issues laws within a particular jurisdiction or location.
- 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_69f349b22d8c819096b22df268382aa9 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f71362f1448190985a80ce7af475cb |
completed | May 3, 2026, 9:20 a.m. |
| PD | Predicate disambiguation | batch_69f7127884388190884f23d181a65d19 |
completed | May 3, 2026, 9:16 a.m. |
Created at: May 1, 2026, 1:56 a.m.