Triple
T16882840
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Third Class, Second Grade |
E421462
|
entity |
| Predicate | gradingStructure |
P21499
|
FINISHED |
| Object | multi-class, multi-grade order |
—
|
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: multi-class, multi-grade order | Statement: [Third Class, Second Grade, gradingStructure, multi-class, multi-grade order]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gradingStructure Context triple: [Third Class, Second Grade, gradingStructure, multi-class, multi-grade order]
-
A.
gradeStructure
chosen
Indicates the hierarchical organization or breakdown of grades or scoring components within an evaluation system.
-
B.
gradeHierarchy
Indicates a hierarchical relationship between grades or levels, where one grade is ranked above or below another in an ordered structure.
-
C.
levelStructure
Indicates that one entity defines or organizes the hierarchical or layered arrangement of another entity.
-
D.
hasAtGradeStructure
Indicates that one entity includes or is associated with a structure located at ground level (at grade).
-
E.
branchStructure
Indicates how the parts of a branching system are organized and connected relative to one another.
- 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_69d889d470fc8190b4aec199636c0c56 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e3bbbdffd8819093f1efd91f6d49dc |
completed | April 18, 2026, 5:13 p.m. |
| PD | Predicate disambiguation | batch_69e32b90ec3c819099c51bb7baf2984c |
completed | April 18, 2026, 6:58 a.m. |
Created at: April 10, 2026, 5:29 a.m.