Triple
T28555023
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bagrut |
E722980
|
entity |
| Predicate | eligibilityForUniversity |
P61327
|
FINISHED |
| Object | full Bagrut certificate |
—
|
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: full Bagrut certificate | Statement: [Bagrut, eligibilityForUniversity, full Bagrut certificate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eligibilityForUniversity Context triple: [Bagrut, eligibilityForUniversity, full Bagrut certificate]
-
A.
hasHigherEducationAccess
chosen
Indicates that one entity has access to higher education opportunities or institutions relative to another entity or context.
-
B.
eligibleInstitution
Indicates that an institution satisfies specified criteria or requirements to qualify for a particular program, benefit, or status.
-
C.
isInCollege
Indicates that a person is currently enrolled as a student at a college or university.
-
D.
connectsToCollege
Indicates a relationship where an entity has a direct link, affiliation, or pathway to a college.
-
E.
hasHigherEducationType
Indicates that one entity has a specified type or category of higher education associated with it.
- 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_69f6aaf50be08190a2b62a6d881f8aee |
completed | May 3, 2026, 1:55 a.m. |
| PD | Predicate disambiguation | batch_69f6aa1c555081908787dbf76147f180 |
completed | May 3, 2026, 1:51 a.m. |
Created at: April 28, 2026, 3:45 a.m.