Triple
T27786084
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tehiya |
E700963
|
entity |
| Predicate | enteredParliament |
P81398
|
FINISHED |
| Object | Knesset |
—
|
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: Knesset | Statement: [Tehiya, enteredParliament, Knesset]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: enteredParliament Context triple: [Tehiya, enteredParliament, Knesset]
-
A.
servedInParliament
Indicates that a person has held a position as a member of a parliamentary body during some period of time.
-
B.
parliamentEntry
chosen
Indicates that an entity assumes or is granted membership or a seat in a parliamentary body.
-
C.
representedInParliamentSince
Indicates that an entity has held representation in a parliament continuously from a specified starting time.
-
D.
servedInParliamentFor
Indicates that a person held a parliamentary seat as a representative of a specified constituency, region, or jurisdiction.
-
E.
hadParliamentaryRepresentationIn
Indicates that an entity was represented by one or more members in a specified parliament or legislative body during a given time or period.
- 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_69ef6a50d8088190acbf3dfbb06d8091 |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f63fd6c68481908c542aa03e297b9c |
completed | May 2, 2026, 6:17 p.m. |
| PD | Predicate disambiguation | batch_69f63c6895f0819088655277e45859a8 |
completed | May 2, 2026, 6:03 p.m. |
Created at: April 27, 2026, 5:24 p.m.