Triple
T15784212
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Drillers |
E382693
|
entity |
| Predicate | representsGradeLevels |
P3870
|
FINISHED |
| Object | 9–12 |
—
|
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: 9–12 | Statement: [Drillers, representsGradeLevels, 9–12]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: representsGradeLevels Context triple: [Drillers, representsGradeLevels, 9–12]
-
A.
denotesGradeLevel
Indicates that one entity specifies or assigns the educational grade level associated with another entity.
-
B.
eligibleGradeLevels
Indicates the grade levels for which something (such as a program, course, or benefit) is considered eligible or applicable.
-
C.
servesGradeLevels
chosen
Indicates that an entity (such as a school or program) provides services or instruction to students in the specified grade levels.
-
D.
regulatesGradeLevels
Indicates a relationship where one entity sets or enforces rules or standards governing the grade levels of another entity.
-
E.
eligibilityGradeLevel
Indicates the grade level or range of grade levels for which an entity is considered eligible or appropriate.
- 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_69d86da16e188190b89af699f1ed0bfe |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e05401c4788190a31c180953433db9 |
completed | April 16, 2026, 3:14 a.m. |
| PD | Predicate disambiguation | batch_69e00537bd1c81908d6e832792fd934f |
completed | April 15, 2026, 9:37 p.m. |
Created at: April 10, 2026, 4:48 a.m.