Triple
T30072608
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Deryck Cooke |
E764225
|
entity |
| Predicate | completedWorkOn |
P107713
|
FINISHED |
| Object | performing version of Mahler’s Tenth Symphony |
—
|
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: performing version of Mahler’s Tenth Symphony | Statement: [Deryck Cooke, completedWorkOn, performing version of Mahler’s Tenth Symphony]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: completedWorkOn Context triple: [Deryck Cooke, completedWorkOn, performing version of Mahler’s Tenth Symphony]
-
A.
completedIn
Indicates that an action, process, or task was fully finished within a specified time period or duration.
-
B.
concludesWork
chosen
Indicates that an entity finishes, completes, or brings to an end a particular piece of work or task.
-
C.
workCompletedAfter
Indicates that one entity’s work or task was finished at a later time than another specified work or task.
-
D.
workOnItEnded
Indicates that an entity’s involvement in working on a particular task, project, or item has come to an end.
-
E.
completedBefore
Indicates that one event or action was fully completed prior to the start or completion of another specified event or action.
- 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_69f22472eee081909791dc372aa766e9 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6b903538481909cffcb6cc1cc0e70 |
completed | May 3, 2026, 2:54 a.m. |
| PD | Predicate disambiguation | batch_69f6b626120c819097c9ad04487570d7 |
completed | May 3, 2026, 2:42 a.m. |
Created at: April 29, 2026, 7:01 p.m.