Triple
T27994266
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Honors College |
E706964
|
entity |
| Predicate | hasTypeOfCoursework |
P189427
|
FINISHED |
| Object | honors courses |
—
|
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: honors courses | Statement: [Honors College, hasTypeOfCoursework, honors courses]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypeOfCoursework Context triple: [Honors College, hasTypeOfCoursework, honors courses]
-
A.
hasTypicalCourse
Indicates that there is a characteristic or commonly observed progression, sequence, or development pattern associated with the subject.
-
B.
hasStructureOnCourse
Indicates that a physical structure is located on, along, or directly associated with a specific course or route.
-
C.
hasCourseThrough
Indicates that something (such as a path, route, or flow) passes through or traverses another entity or area.
-
D.
hasPrimaryCourse
Indicates that an entity is associated with its main or principal course in a given context (such as a meal, curriculum, or sequence of offerings).
-
E.
isCourse
Indicates that an entity functions as or qualifies as a course within a given context or system.
- 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_69ef96b980d88190a753b2f9a978595a |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69fbc36ce1f88190a7fa1656b714e107 |
completed | May 6, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69fbbd13595c81908719f52c3d37a7e8 |
completed | May 6, 2026, 10:13 p.m. |
| PDg | Predicate description generation | batch_69fbc36bcac48190a726b40442c094d1 |
completed | May 6, 2026, 10:40 p.m. |
Created at: April 27, 2026, 7:52 p.m.