Triple
T29807642
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Harmony Codex |
E756878
|
entity |
| Predicate | hasContributor |
P4244
|
FINISHED |
| Object |
Craig Blundell
Craig Blundell is a British drummer renowned for his work in progressive rock and fusion, including collaborations with artists like Steven Wilson.
|
E1923452
|
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: Craig Blundell | Statement: [The Harmony Codex, hasContributor, Craig Blundell]
NEDg
Description generation
gpt-5.1
Instruction
Generate a one-sentence description of the target entity. You are given a context triple in the form (subject, predicate, object), where the object is the target entity. # Instructions Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. Avoid repeating the information from the triple, unless really essential. # Response Format Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Craig Blundell Triple: [The Harmony Codex, hasContributor, Craig Blundell]
Generated description
Craig Blundell is a British drummer renowned for his work in progressive rock and fusion, including collaborations with artists like Steven Wilson.
Provenance (5 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_69f2245584848190ad4cab1f07752ccb |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f6752c3da08190b114b1cddc9cc9d3 |
completed | May 2, 2026, 10:05 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a2863b41c30819098c3fed3f892cb85 |
completed | June 9, 2026, 7:04 p.m. |
| NEDg | Description generation | batch_6a28666083a88190a357b9ca7da92343 |
completed | June 9, 2026, 7:15 p.m. |
| NED2 | Entity disambiguation (via description) | batch_6a286727049c8190bcd5d0fef0a3d8b7 |
completed | June 9, 2026, 7:19 p.m. |
Created at: April 29, 2026, 5:22 p.m.