Triple
T37061978
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 大阪工業大学 |
E917345
|
entity |
| Predicate | ロボティクス＆デザイン工学部設置目的 |
P49728
|
FINISHED |
| Object | ロボット技術とデザイン思考を融合した人材育成 |
—
|
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: ロボット技術とデザイン思考を融合した人材育成 | Statement: [大阪工業大学, ロボティクス＆デザイン工学部設置目的, ロボット技術とデザイン思考を融合した人材育成]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ロボティクス＆デザイン工学部設置目的 Context triple: [大阪工業大学, ロボティクス＆デザイン工学部設置目的, ロボット技術とデザイン思考を融合した人材育成]
-
A.
designDiscipline
Indicates a relationship where an entity is associated with, categorized under, or practices a particular field or branch of design.
-
B.
isEngineeringFacultyOf
Indicates that one entity serves as the engineering faculty (academic unit or staff body) associated with, belonging to, or responsible for engineering education and activities at another entity (typically an institution).
-
C.
主な学部
Indicates a relationship where a university or institution is associated with its primary or main academic faculty/department.
-
D.
engineeringGoal
chosen
Indicates that an entity has a specific engineering-related objective, target, or desired outcome it is intended to achieve or support.
-
E.
reasonForDesign
Indicates that one entity serves as the explanation, motivation, or justification for why another entity was designed or created in a particular way.
- 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_69f76e95fa40819091e14681087ae5e4 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb34e5576881909394355c8ec6ddd2 |
completed | May 6, 2026, 12:32 p.m. |
| PD | Predicate disambiguation | batch_69fb2f6171e88190bf1e0ee6a644b6a9 |
completed | May 6, 2026, 12:09 p.m. |
Created at: May 3, 2026, 4:14 p.m.