Triple
T28555019
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bagrut |
E722980
|
entity |
| Predicate | advancedLevelUnits |
P118085
|
FINISHED |
| Object | 5 study units |
—
|
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: 5 study units | Statement: [Bagrut, advancedLevelUnits, 5 study units]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: advancedLevelUnits Context triple: [Bagrut, advancedLevelUnits, 5 study units]
-
A.
advancedThrough
Indicates that an entity has progressed or moved forward within, or as a result of, a particular medium, stage, process, or pathway.
-
B.
upperLevels
Indicates that one entity occupies or corresponds to higher levels, tiers, or hierarchical positions relative to another entity.
-
C.
hasUnitLevel
chosen
Indicates that something is associated with, measured at, or applicable to a specific unit level within a larger hierarchy or scale.
-
D.
basicLevelUnits
Indicates that the related entities are connected through a shared basic-level unit or category that groups them at a fundamental level of classification.
-
E.
upperGrade
Indicates that one entity is in a higher grade level than 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_69f65f7731e4819099d5bd3d915ee266 |
completed | May 2, 2026, 8:32 p.m. |
| PD | Predicate disambiguation | batch_69f65c2198208190a3954086c22cfcbf |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 28, 2026, 3:45 a.m.