Triple
T28554321
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Judicial Selection Committee of Israel |
E722964
|
entity |
| Predicate | appointsJudgesTo |
P19633
|
FINISHED |
| Object | Supreme Court 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: Supreme Court of Israel | Statement: [Judicial Selection Committee of Israel, appointsJudgesTo, Supreme Court of Israel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appointsJudgesTo Context triple: [Judicial Selection Committee of Israel, appointsJudgesTo, Supreme Court of Israel]
-
A.
appointingAuthorityForJudges
chosen
Indicates the entity that has the official power or responsibility to appoint judges.
-
B.
judgesElected
Indicates that the judges in question attained their positions through an electoral process rather than by appointment or other means.
-
C.
hasJudgesAppointedBy
Indicates that one entity serves as a judge who has been formally appointed by another entity.
-
D.
judgeAppointmentBy
Indicates that one entity is appointed to the role of judging or evaluating another entity by a specific authority or process.
-
E.
judgesAre
Indicates that one entity serves as a judge or evaluator of another entity.
- 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_69f01a60204481909af1bb76247b8221 |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69f72921cf2c8190909bb53f78bcc890 |
completed | May 3, 2026, 10:53 a.m. |
| PD | Predicate disambiguation | batch_69f7283d8cec8190b524c144948bc4ec |
completed | May 3, 2026, 10:49 a.m. |
Created at: April 28, 2026, 3:44 a.m.