Triple
T26556111
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lewis Allan |
E671811
|
entity |
| Predicate | workPerformedBy |
P43698
|
FINISHED |
| Object | various jazz musicians |
—
|
LITERAL 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: various jazz musicians | Statement: [Lewis Allan, workPerformedBy, various jazz musicians]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: workPerformedBy Context triple: [Lewis Allan, workPerformedBy, various jazz musicians]
-
A.
performedWorkBy
Indicates that a particular work, task, or activity was carried out or executed by a specified agent or entity.
-
B.
performedInWorkBy
Indicates that an action or role was carried out within a specific work (e.g., a film, book, or composition) by a particular agent or contributor.
-
C.
performsWorkBy
Indicates that one entity carries out or executes work, tasks, or activities on behalf of or as defined by another entity.
-
D.
performsWorksBy
chosen
Indicates that an agent executes, interprets, or presents works that were created or authored by another entity.
-
E.
performsWorkOf
Indicates that one entity carries out, executes, or fulfills the tasks, functions, or role that are normally associated with another entity.
- 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_69eeb32163f08190af5f81282738e27a |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f62d53ad58819080c5227c7a729d15 |
completed | May 2, 2026, 4:58 p.m. |
| PD | Predicate disambiguation | batch_69f62c15952881908a5ea0c25904afec |
completed | May 2, 2026, 4:53 p.m. |
Created at: April 27, 2026, 1:50 a.m.