Triple
T22583347
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Frontiers in Education Conference |
E564719
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | engineering education conference |
C46534
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: engineering education conference Context triple: [Frontiers in Education Conference, instanceOf, engineering education conference]
-
A.
engineering education system
An engineering education system is an organized framework of curricula, instructional methods, resources, and assessment practices designed to develop learners’ technical knowledge, problem-solving skills, and professional competencies in engineering disciplines.
-
B.
engineering education centre
An engineering education centre is a dedicated facility that supports the teaching, learning, and practical application of engineering principles through classrooms, laboratories, workshops, and collaborative spaces.
-
C.
engineering institute
An engineering institute is an educational and research organization dedicated to teaching, advancing, and applying engineering principles and technologies across various specialized fields.
-
D.
engineering school faculty
Engineering school faculty are academic professionals who teach, mentor, and conduct research in engineering disciplines while contributing to curriculum development and institutional service.
-
E.
engineering student society
An engineering student society is a student-run organization that supports engineering students’ academic, professional, and social development through events, resources, and community-building activities.
- F. None of above. chosen
Provenance (1 batch)
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_69e245836014819091b91ed3074742a3 |
completed | April 17, 2026, 2:36 p.m. |
Created at: April 17, 2026, 2:41 p.m.