Triple
T10008933
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Clogs |
E198320
|
entity |
| Predicate | performsTypeOfWork |
P1366
|
FINISHED |
| Object | instrumental compositions |
—
|
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: instrumental compositions | Statement: [Clogs, performsTypeOfWork, instrumental compositions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: performsTypeOfWork Context triple: [Clogs, performsTypeOfWork, instrumental compositions]
-
A.
performsWorkOf
Indicates that one entity carries out, executes, or fulfills the tasks, functions, or role that are normally associated with another entity.
-
B.
performsWork
Indicates that one entity carries out, executes, or engages in work or tasks for or on behalf of another entity or context.
-
C.
performsWorkBy
Indicates that one entity carries out or executes work, tasks, or activities on behalf of or as defined by another entity.
-
D.
typeOfWork
chosen
Indicates the kind or category of work associated with or performed by an entity.
-
E.
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.
- 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_69ca830fcca48190bbbd9b20c233835f |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cdcd38659c8190830d223edbfd74ec |
completed | April 2, 2026, 1:58 a.m. |
| PD | Predicate disambiguation | batch_69cd1da2cf9081908a6c0eb5247d0bc2 |
completed | April 1, 2026, 1:29 p.m. |
Created at: March 30, 2026, 8:52 p.m.