Triple
T12761703
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Master of Finance |
E305010
|
entity |
| Predicate | typicalCoreCourse |
P11940
|
FINISHED |
| Object | corporate finance |
—
|
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: corporate finance | Statement: [Master of Finance, typicalCoreCourse, corporate finance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalCoreCourse Context triple: [Master of Finance, typicalCoreCourse, corporate finance]
-
A.
typicalCourse
chosen
Indicates that one entity is a standard or commonly taken course associated with another entity, such as a program, curriculum, or field of study.
-
B.
typicalCourseTopic
Indicates that a given topic is commonly or characteristically covered as part of a particular course.
-
C.
typicalCoreType
Indicates that something is a standard or characteristic core type within a given classification or system.
-
D.
courseType
Indicates the classification or category of a course based on its nature, level, or instructional format.
-
E.
notableCourseType
Indicates that a course has a particular notable or distinguished type or classification (e.g., flagship, honors, or otherwise specially recognized).
- 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_69d7bdf1fcd081909ffb0e0d6fa3a07d |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d96d8e44188190840cd23d380bf23d |
completed | April 10, 2026, 9:37 p.m. |
| PD | Predicate disambiguation | batch_69d96409739881909174ba005a986cb5 |
completed | April 10, 2026, 8:56 p.m. |
Created at: April 9, 2026, 5:28 p.m.