Triple
T24149106
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ponevezh Yeshiva |
E598476
|
entity |
| Predicate | reestablishedCountry |
P154788
|
FINISHED |
| Object | 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: Israel | Statement: [Ponevezh Yeshiva, reestablishedCountry, Israel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reestablishedCountry Context triple: [Ponevezh Yeshiva, reestablishedCountry, Israel]
-
A.
rejoinedCountry
Indicates that an entity has become part of a country again after having previously separated or left it.
-
B.
reestablishedInYear
Indicates that an entity, previously existing and then discontinued or dissolved, was brought back into existence or operation in the specified year.
-
C.
countrySucceededBy
Indicates that one country is the direct successor state that replaces or follows another country in sovereignty or political continuity.
-
D.
rejoinedCountryYear
Indicates the year in which an entity re-entered or rejoined a particular country after having previously left or been separated from it.
-
E.
countryAfterSuccession
Indicates that one country is the successor state that takes over from another country after a political or territorial succession.
- 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_69e288c9e488819093dd1acd91b08b8a |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1e00d252c8190a02bec29189baad0 |
completed | April 29, 2026, 10:40 a.m. |
| PD | Predicate disambiguation | batch_69f176585f3481909beb907de252cd98 |
completed | April 29, 2026, 3:09 a.m. |
| PDg | Predicate description generation | batch_69f1785afe3c81909be28986ffe944bf |
completed | April 29, 2026, 3:17 a.m. |
Created at: April 17, 2026, 11:30 p.m.