Triple
T37844249
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 李遠哲 |
E943560
|
entity |
| Predicate | 博士指導教授 |
P138222
|
FINISHED |
| Object | Bruce H. Mahan |
—
|
NE NERFINISHED |
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: Bruce H. Mahan | Statement: [李遠哲, 博士指導教授, Bruce H. Mahan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: 博士指導教授 Context triple: [李遠哲, 博士指導教授, Bruce H. Mahan]
-
A.
professor
chosen
Indicates that one entity holds the role or position of professor in relation to another entity (such as an institution, course, or student).
-
B.
postdoctoralAdvisor
Indicates that one person served as the postdoctoral research advisor or mentor to another person.
-
C.
academicChair
Indicates that one entity serves as the academic chair (leader or head) of a department, program, or academic unit associated with the other entity.
-
D.
hasDoctoralStudentsThrough
Indicates that one entity has doctoral students indirectly through another entity, such as via co-supervision, program affiliation, or intermediary supervision relationships.
-
E.
academicHead
Indicates that one entity serves as the chief academic leader or head of another entity, such as a department, program, or institution.
- 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_69f76eeb0f7081908d6d3adbc469889c |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fbbae559a8819086ef839973f8d9b2 |
completed | May 6, 2026, 10:04 p.m. |
| PD | Predicate disambiguation | batch_69fbb1440fa08190abf25ba684f75b6e |
completed | May 6, 2026, 9:23 p.m. |
Created at: May 3, 2026, 4:19 p.m.