Triple
T37106130
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Perchik |
E918845
|
entity |
| Predicate | composerAssociatedWork |
P150455
|
FINISHED |
| Object | Jerry Bock |
—
|
NE NERFINISHED |
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: Jerry Bock | Statement: [Perchik, composerAssociatedWork, Jerry Bock]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: composerAssociatedWork Context triple: [Perchik, composerAssociatedWork, Jerry Bock]
-
A.
associatedWithAuthorWork
Indicates a relationship where an author is connected to a work they created, contributed to, or are otherwise credited for.
-
B.
composerOfRelatedWorks
chosen
Indicates that an entity is the composer of works that are related to another specified work or set of works.
-
C.
composerOfWorkAppearsIn
Indicates that a person is the composer of a musical or artistic work that appears within another work or context.
-
D.
relatedToAuthorWork
Indicates that there is a connection or association between an author and a work they have created, contributed to, or are otherwise linked with.
-
E.
appearsInWorkByAuthorFrom
Indicates that an entity appears in a work that was created by an author originating from a specified place or country.
- 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_69f76e9b99c8819096164b21ff5bd996 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fe00dad1708190b6522476bebb43af |
completed | May 8, 2026, 3:27 p.m. |
| PD | Predicate disambiguation | batch_69fdfc3717f48190bb50ac2919c8ef95 |
completed | May 8, 2026, 3:07 p.m. |
Created at: May 3, 2026, 4:14 p.m.