Triple
T22804108
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lyndhurst Golden Bears |
E564484
|
entity |
| Predicate | hasStudentAthletesFromGrades |
P98368
|
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: [Lyndhurst Golden Bears, hasStudentAthletesFromGrades, 9–12]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStudentAthletesFromGrades Context triple: [Lyndhurst Golden Bears, hasStudentAthletesFromGrades, 9–12]
-
A.
hasNumberOfStudentAthletes
Indicates the relationship that specifies how many student athletes are associated with a given entity.
-
B.
hasGradesOrClasses
Indicates that an entity is associated with academic evaluations or enrolled instructional sessions, such as grades received or classes taken.
-
C.
includesGrades
Indicates that one entity contains or encompasses the grade information associated with another entity.
-
D.
eligibleGradeLevels
chosen
Indicates the grade levels for which something (such as a program, course, or benefit) is considered eligible or applicable.
-
E.
hasGrades
Indicates that an entity possesses or is associated with one or more grade values, typically reflecting evaluations or scores.
- 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_69e245823f4c8190ade442cdcc2c224a |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17d5a7c2881909a7aaacddd09f00c |
completed | April 29, 2026, 3:39 a.m. |
| PD | Predicate disambiguation | batch_69eed2cb30f481909566369f515f6eff |
completed | April 27, 2026, 3:06 a.m. |
Created at: April 17, 2026, 3:31 p.m.