Triple
T29371349
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Concert sans orchestre |
E744861
|
entity |
| Predicate | workTitleByComposer |
P40533
|
FINISHED |
| Object | Concert sans orchestre |
—
|
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: Concert sans orchestre | Statement: [Concert sans orchestre, workTitleByComposer, Concert sans orchestre]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: workTitleByComposer Context triple: [Concert sans orchestre, workTitleByComposer, Concert sans orchestre]
-
A.
producedComposer
Indicates that one entity served as the producer for a musical work created or composed by another entity.
-
B.
workComposer
Indicates that one entity is the composer or creator of a musical or artistic work represented by the other entity.
-
C.
partOfComposerOeuvre
chosen
Indicates that a musical work belongs to and is included within the overall body of compositions created by a particular composer.
-
D.
catalogueOfComposer
Indicates that one entity is a catalogue that systematically lists or documents the works of a particular composer.
-
E.
notableComposerRole
Indicates that the subject has a significant or distinguished role as a composer in relation to the object.
- 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_69f0a79ba954819094597628112c6091 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69f66d7765208190b87b1cc6d96a151c |
completed | May 2, 2026, 9:32 p.m. |
| PD | Predicate disambiguation | batch_69f66abfdaf08190a55f14c70be6fd4d |
completed | May 2, 2026, 9:21 p.m. |
Created at: April 28, 2026, 2:27 p.m.