Triple
T21738050
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Texas Tech University Independent School District |
E536576
|
entity |
| Predicate | offersAssessmentType |
P86246
|
FINISHED |
| Object | online exams |
—
|
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: online exams | Statement: [Texas Tech University Independent School District, offersAssessmentType, online exams]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: offersAssessmentType Context triple: [Texas Tech University Independent School District, offersAssessmentType, online exams]
-
A.
offersQualificationType
Indicates that an entity provides or makes available a specific type or category of qualification.
-
B.
offersEnrollmentType
Indicates that an entity provides or makes available a specific type or category of enrollment option.
-
C.
offersCourseType
Indicates that an entity provides or makes available a course of a specified type.
-
D.
offersExaminations
chosen
Indicates that one entity provides or makes available examinations or tests to another entity.
-
E.
offersPlanType
Indicates that one entity provides or makes available a specific type of plan to another entity or in a given context.
- 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_69e0c46df5448190b4322127ffc4c690 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69effd0d33dc81908a4a79abc33355d1 |
completed | April 28, 2026, 12:19 a.m. |
| PD | Predicate disambiguation | batch_69e6969c16fc8190b5126c169317d85d |
completed | April 20, 2026, 9:11 p.m. |
Created at: April 16, 2026, 6:49 p.m.