Triple
T28555014
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bagrut |
E722980
|
entity |
| Predicate | higherAchievementThreshold |
P22279
|
FINISHED |
| Object | 85 |
—
|
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: 85 | Statement: [Bagrut, higherAchievementThreshold, 85]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: higherAchievementThreshold Context triple: [Bagrut, higherAchievementThreshold, 85]
-
A.
achievementLevel
Indicates the degree or extent to which an entity has attained a particular goal, standard, or performance outcome.
-
B.
highestPass
Indicates that an entity has achieved the greatest passing value, score, or level among a set of compared entities.
-
C.
requiresMinimumScore
chosen
Indicates that one entity can only be obtained, accessed, or considered valid if another entity’s score meets or exceeds a specified minimum threshold.
-
D.
becameHighA
Indicates that an entity transitioned into a state or role characterized as "HighA" (e.g., gaining a higher level, status, or attribute A).
-
E.
achievementScope
Indicates the extent or domain within which an achievement is recognized, measured, or considered valid.
- 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_69f6fb19063c81909466b329655c8583 |
completed | May 3, 2026, 7:36 a.m. |
| PD | Predicate disambiguation | batch_69f6f969b4cc8190afb473a2d8b110bc |
completed | May 3, 2026, 7:29 a.m. |
Created at: April 28, 2026, 3:45 a.m.