Triple
T26807631
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dixie Technical College |
E671883
|
entity |
| Predicate | offersScheduleOption |
P167715
|
FINISHED |
| Object | day programs |
—
|
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: day programs | Statement: [Dixie Technical College, offersScheduleOption, day programs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: offersScheduleOption Context triple: [Dixie Technical College, offersScheduleOption, day programs]
-
A.
offersSchedule
Indicates that one entity provides or makes available a specific schedule to another entity or for a particular purpose.
-
B.
offersProgramMode
chosen
Indicates that one entity provides or makes available a specific program mode or operational mode to another entity or for a particular context.
-
C.
offersProgram
Indicates that an entity provides or makes available a specific program (such as a course, curriculum, or initiative).
-
D.
offersDayProgram
Indicates that an entity provides a structured program or service that takes place during daytime hours.
-
E.
offersEdition
Indicates that one entity provides or makes available a particular version or edition of another entity.
- 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_69eeb3225a3c8190aaf6746efeded2f3 |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f7221dc9a88190bb8194fcc29c42bc |
completed | May 3, 2026, 10:23 a.m. |
| PD | Predicate disambiguation | batch_69f72153a9188190b02adc84e1be4af8 |
completed | May 3, 2026, 10:20 a.m. |
Created at: April 27, 2026, 4:27 a.m.