Triple
T36412873
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Magical Me |
E896927
|
entity |
| Predicate | professorUsing |
P63933
|
FINISHED |
| Object | Gilderoy Lockhart |
—
|
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: Gilderoy Lockhart | Statement: [Magical Me, professorUsing, Gilderoy Lockhart]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: professorUsing Context triple: [Magical Me, professorUsing, Gilderoy Lockhart]
-
A.
professor
Indicates that one entity holds the role or position of professor in relation to another entity (such as an institution, course, or student).
-
B.
usesInTeaching
chosen
Indicates that an agent employs a particular resource, method, or material as part of their teaching activities.
-
C.
isProfessorshipIn
Indicates that a professorship position is associated with or belongs to a specific academic field, department, or institution.
-
D.
usedByFaculty
Indicates that something is utilized or employed by faculty members in carrying out their roles or activities.
-
E.
notableProfessor
Indicates that a person holds or has held a professorship that is distinguished, prominent, or otherwise recognized as notable.
- 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_69f76e54ce408190849acc3f7758937c |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7be9d07ac8190adf796cbef60daf6 |
completed | May 3, 2026, 9:31 p.m. |
| PD | Predicate disambiguation | batch_69f7bcccd7988190aa5c931ff347d33c |
completed | May 3, 2026, 9:23 p.m. |
Created at: May 3, 2026, 4:10 p.m.