Triple
T36602212
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Central City Opera |
E902947
|
entity |
| Predicate | commissionedWorkComposer |
P134617
|
FINISHED |
| Object | Douglas Moore |
—
|
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: Douglas Moore | Statement: [Central City Opera, commissionedWorkComposer, Douglas Moore]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commissionedWorkComposer Context triple: [Central City Opera, commissionedWorkComposer, Douglas Moore]
-
A.
commissionedComposer
chosen
Indicates that one entity formally requested and funded another entity (a composer) to create a musical work.
-
B.
dedicatedComposerWork
Indicates that a particular work was specifically created or formally dedicated by the composer to a person, group, or entity.
-
C.
workComposer
Indicates that one entity is the composer or creator of a musical or artistic work represented by the other entity.
-
D.
employedComposer
Indicates that one entity (such as a person or organization) employs another entity in the role of a composer.
-
E.
producedComposer
Indicates that one entity served as the producer for a musical work created or composed by 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_69f76e66b7b88190848f7a3e1188915f |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7c30d4a1c8190b94b8b6f30184472 |
completed | May 3, 2026, 9:50 p.m. |
| PD | Predicate disambiguation | batch_69f7c1bbf5848190a698fdbec307886a |
completed | May 3, 2026, 9:44 p.m. |
Created at: May 3, 2026, 4:11 p.m.