Triple
T23538716
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New Directions |
E577678
|
entity |
| Predicate | facultyAdvisor |
P167
|
FINISHED |
| Object | Will Schuester |
—
|
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: Will Schuester | Statement: [New Directions, facultyAdvisor, Will Schuester]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: facultyAdvisor Context triple: [New Directions, facultyAdvisor, Will Schuester]
-
A.
academicAdvisor
chosen
Indicates that one entity serves as the academic advisor, providing formal guidance and oversight on academic matters, to another entity.
-
B.
academicAdvisorOfAuthor
Indicates that one person serves as the academic advisor or mentor responsible for guiding the author in their scholarly or research activities.
-
C.
professor
Indicates that one entity holds the role or position of professor in relation to another entity (such as an institution, course, or student).
-
D.
associatedWithAdvisor
Indicates that an entity has a relationship of guidance, oversight, or mentorship with a designated advisor.
-
E.
postdoctoralAdvisor
Indicates that one person served as the postdoctoral research advisor or mentor to another person.
- 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_69e245f9d5d08190a4a20004e1784e20 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f1ae19473881909aa65f9d36744502 |
completed | April 29, 2026, 7:07 a.m. |
| PD | Predicate disambiguation | batch_69f118afabd88190bd88f49597d120e8 |
completed | April 28, 2026, 8:29 p.m. |
Created at: April 17, 2026, 6:10 p.m.