Triple
T17609176
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tamalpais Union High School District |
E428921
|
entity |
| Predicate | overseesGrades |
P128260
|
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: [Tamalpais Union High School District, overseesGrades, 9–12]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: overseesGrades Context triple: [Tamalpais Union High School District, overseesGrades, 9–12]
-
A.
hasGrades
Indicates that an entity possesses or is associated with one or more grade values, typically reflecting evaluations or scores.
-
B.
grades
Indicates that one entity evaluates and assigns a score or level of performance to another entity.
-
C.
isGradedBy
Indicates that an entity (such as an assignment, exam, or work) is evaluated and assigned a grade by another entity (such as a person, system, or organization).
-
D.
gradingSystem
Indicates the method or criteria by which performance, quality, or achievement is evaluated and assigned a grade or score.
-
E.
gradeIn
Indicates that an entity has a particular grade or score within a specified course, assignment, or evaluation context.
- 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_69d889e1c6148190ba76241e74688f8b |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e46c4e6ba48190804e113983e7c704 |
completed | April 19, 2026, 5:46 a.m. |
| PD | Predicate disambiguation | batch_69e3cdd7da34819099bc9481c5a79bab |
completed | April 18, 2026, 6:30 p.m. |
| PDg | Predicate description generation | batch_69e3cfaac2b881909e1140339eb1a0dd |
completed | April 18, 2026, 6:38 p.m. |
Created at: April 10, 2026, 5:51 a.m.