Triple
T17260157
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Third Class, First Grade |
E418987
|
entity |
| Predicate | gradeWithinClass |
P126755
|
FINISHED |
| Object | First Grade |
—
|
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: First Grade | Statement: [Third Class, First Grade, gradeWithinClass, First Grade]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gradeWithinClass Context triple: [Third Class, First Grade, gradeWithinClass, First Grade]
-
A.
gradeWithin
Indicates that one value’s grade or level falls within a specified range or interval relative to another.
-
B.
gradeCategory
Indicates the classification of a grade into a broader category or level (such as letter grade, performance band, or pass/fail group).
-
C.
gradeIn
Indicates that an entity has a particular grade or score within a specified course, assignment, or evaluation context.
-
D.
gradeNumber
Indicates the numerical grade or level assigned to an entity within an ordered grading or classification system.
-
E.
gradeRank
Indicates the relative academic standing or position of an entity within a graded or ranked group based on performance or scores.
- 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_69d886d9ab108190b70edd8d17aa1204 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e42e6fa940819089046d1b12dede2c |
completed | April 19, 2026, 1:22 a.m. |
| PD | Predicate disambiguation | batch_69e3832a284481908a8a3da7ac91de5a |
completed | April 18, 2026, 1:12 p.m. |
| PDg | Predicate description generation | batch_69e39c2fedb881908bfed2c3e5f2616a |
completed | April 18, 2026, 2:58 p.m. |
Created at: April 10, 2026, 5:39 a.m.