Triple
T441646
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | edX |
E10125
|
entity |
| Predicate | hasTypeOfCourse |
P6650
|
FINISHED |
| Object | computer science |
—
|
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: computer science | Statement: [edX, hasTypeOfCourse, computer science]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypeOfCourse Context triple: [edX, hasTypeOfCourse, computer science]
-
A.
offersCourseType
chosen
Indicates that an entity provides or makes available a course of a specified type.
-
B.
courseType
Indicates the classification or category of a course based on its nature, level, or instructional format.
-
C.
typicalCourse
Indicates that one entity is a standard or commonly taken course associated with another entity, such as a program, curriculum, or field of study.
-
D.
hasFacultyType
Indicates that a faculty member or academic unit is associated with a specific category or type of faculty (e.g., full-time, adjunct, visiting).
-
E.
isStudiedIn
Indicates that a subject (such as a topic, field, or phenomenon) is examined, researched, or learned about within a particular context, environment, or discipline.
- 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_69a2e8465ef481909655c681b01e2986 |
completed | Feb. 28, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69a2ef42b4008190abed9d79926c7022 |
completed | Feb. 28, 2026, 1:36 p.m. |
| PD | Predicate disambiguation | batch_69a2eddcf50c8190bfa0d1f8ee9f604a |
completed | Feb. 28, 2026, 1:30 p.m. |
Created at: Feb. 28, 2026, 1:11 p.m.