Triple
T33301584
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rudimental Ritual |
E852596
|
entity |
| Predicate | notableStudentPractitioner |
P4838
|
FINISHED |
| Object | Tony Williams |
E154648
|
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: Tony Williams | Statement: [Rudimental Ritual, notableStudentPractitioner, Tony Williams]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableStudentPractitioner Context triple: [Rudimental Ritual, notableStudentPractitioner, Tony Williams]
-
A.
notablePractitioner
Indicates that an entity is a well-known or distinguished practitioner of a particular field, discipline, or activity.
-
B.
notableStudent
chosen
Indicates that a person is a distinguished or particularly significant student of another individual or institution.
-
C.
notableStudentOrColleague
Indicates that one entity is a notable student or professional colleague of another entity.
-
D.
notableLecturer
Indicates that a person is recognized as a distinguished or prominent lecturer, often due to their expertise, impact, or reputation in giving lectures.
-
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_6a354323dce08190a0343f4485f8ad2e |
completed | June 19, 2026, 1:24 p.m. |
| PD | Predicate disambiguation | batch_6a0379f338b881908e5593e45d764f4d |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:33 a.m.