Triple
T29842529
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Moor (Petrushka) |
E757839
|
entity |
| Predicate | composerOfWorkCreator |
P84165
|
FINISHED |
| Object | Igor Stravinsky |
—
|
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: Igor Stravinsky | Statement: [The Moor (Petrushka), composerOfWorkCreator, Igor Stravinsky]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: composerOfWorkCreator Context triple: [The Moor (Petrushka), composerOfWorkCreator, Igor Stravinsky]
-
A.
composerOfWorkAppearsIn
Indicates that a person is the composer of a musical or artistic work that appears within another work or context.
-
B.
createdWork
Indicates that an agent is responsible for bringing a work (such as a creative, intellectual, or produced artifact) into existence.
-
C.
workComposer
chosen
Indicates that one entity is the composer or creator of a musical or artistic work represented by the other entity.
-
D.
creativeWorkOn
Indicates a relationship where an entity has created, contributed to, or worked on a particular creative work (such as a book, artwork, film, or other intellectual product).
-
E.
coCreator
Indicates that two or more entities jointly created or produced something together.
- 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_69f224593f6c81908785a560fe659f58 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f760a35b988190904e6267553ad2fe |
completed | May 3, 2026, 2:50 p.m. |
| PD | Predicate disambiguation | batch_69f75eb3d6f081908c933474eb359e3d |
completed | May 3, 2026, 2:41 p.m. |
Created at: April 29, 2026, 5:40 p.m.