Triple
T16712505
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MechE |
E406141
|
entity |
| Predicate | commonCoursework |
P31908
|
FINISHED |
| Object | statics |
—
|
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: statics | Statement: [MechE, commonCoursework, statics]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commonCoursework Context triple: [MechE, commonCoursework, statics]
-
A.
coursePar
Indicates that two entities (such as paths, lines, or trajectories) run alongside each other in the same general direction without intersecting.
-
B.
course
Indicates that an entity is an academic class or unit of instruction offered within an educational program.
-
C.
commonlyTaughtWith
chosen
Indicates that two subjects or concepts are frequently taught together within the same course, lesson, or curriculum context.
-
D.
typicalStudentAssignment
Indicates that an assignment is a standard or commonly expected task given to a student in a particular educational context.
-
E.
courseUse
Indicates that a course employs, incorporates, or makes use of a particular resource, tool, or material in its instruction or structure.
- 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_69d8838db21081909589220fd71440a4 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e386530d9c8190b91ec3aac7dc2518 |
completed | April 18, 2026, 1:25 p.m. |
| PD | Predicate disambiguation | batch_69e319c379f88190ac0adf812486f598 |
completed | April 18, 2026, 5:42 a.m. |
Created at: April 10, 2026, 5:20 a.m.