Triple
T24372681
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Toledo Rockets |
E614377
|
entity |
| Predicate | haveStudentSection |
P20915
|
FINISHED |
| Object | Yes |
—
|
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: Yes | Statement: [Toledo Rockets, haveStudentSection, Yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: haveStudentSection Context triple: [Toledo Rockets, haveStudentSection, Yes]
-
A.
hasStudentSection
chosen
Indicates that an entity (such as a course or class) is associated with a specific student section or subgroup of enrolled students.
-
B.
studentSection
Indicates a relationship where a student is enrolled in or associated with a particular course section.
-
C.
hasStudents
Indicates that an entity (such as a class, school, or teacher) is associated with one or more students.
-
D.
hasStudentCategory
Indicates that an entity is classified under a specific category or type of student.
-
E.
studentSectionName
Indicates that a given student is associated with a specific class section identified by its name.
- 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_69e2d7e1e010819098b95eb3f905943d |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f293d462f88190bf95a83274d8a850 |
completed | April 29, 2026, 11:27 p.m. |
| PD | Predicate disambiguation | batch_69f287bb1b2c81909c2e7fcc392ad143 |
completed | April 29, 2026, 10:35 p.m. |
Created at: April 18, 2026, 2:02 a.m.