Triple
T29326174
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grohg |
E743649
|
entity |
| Predicate | hasRoleInOeuvre |
P27764
|
FINISHED |
| Object | precursor to later Copland works |
—
|
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: precursor to later Copland works | Statement: [Grohg, hasRoleInOeuvre, precursor to later Copland works]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRoleInOeuvre Context triple: [Grohg, hasRoleInOeuvre, precursor to later Copland works]
-
A.
hasAuthorRoleFor
Indicates that an entity serves in the role of author for another entity, such as a work, document, or publication.
-
B.
partOfArtistOeuvre
Indicates that something (such as a work or piece) belongs to and is included within an artist’s overall body of work.
-
C.
composerOfWorkAppearsIn
Indicates that a person is the composer of a musical or artistic work that appears within another work or context.
-
D.
hasNotableRoleIn
chosen
Indicates that an entity holds a significant or noteworthy role or function within another entity, event, work, or context.
-
E.
belongsToAuthorOeuvrePhase
Indicates that something is part of a specific phase within an author's overall body of work.
- 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_69f09125f784819080f4e9fce9fe624f |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69f7bbf906d8819099020e548dd56bc9 |
completed | May 3, 2026, 9:19 p.m. |
| PD | Predicate disambiguation | batch_69f7b9a2dcf88190a7c9e109e41267be |
completed | May 3, 2026, 9:09 p.m. |
Created at: April 28, 2026, 1:26 p.m.