Triple
T33301583
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rudimental Ritual |
E852596
|
entity |
| Predicate | notableTeacherOfMethod |
P140520
|
FINISHED |
| Object | Alan Dawson |
E241172
|
NE 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: Alan Dawson | Statement: [Rudimental Ritual, notableTeacherOfMethod, Alan Dawson]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableTeacherOfMethod Context triple: [Rudimental Ritual, notableTeacherOfMethod, Alan Dawson]
-
A.
notableFormerTeacher
Indicates that one entity previously taught another and is recognized as a particularly significant or distinguished former teacher of that entity.
-
B.
notableTeaching
Indicates that one entity is recognized for having taught, instructed, or educated another entity in a notable or significant way.
-
C.
taughtPosthumouslyTo
Indicates that instruction or teaching was provided to someone only after the teacher’s death.
-
D.
traditionallyTaughtBy
chosen
Indicates that something is customarily or historically instructed or passed down by a particular person, group, or institution.
-
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 (4 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_69f34966ed4c81908dc9dda82d8c7fe3 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a037c8ae0248190b7e2ce4bf852c22d |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a359592e6088190b0a8b3e00604b1ed |
completed | June 19, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379f338b881908e5593e45d764f4d |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:33 a.m.