Triple
T38386938
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Concerts Lamoureux |
E899603
|
entity |
| Predicate | premieredComposerWork |
P182409
|
FINISHED |
| Object | Claude Debussy – La Mer |
—
|
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: Claude Debussy – La Mer | Statement: [Concerts Lamoureux, premieredComposerWork, Claude Debussy – La Mer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: premieredComposerWork Context triple: [Concerts Lamoureux, premieredComposerWork, Claude Debussy – La Mer]
-
A.
composerOfPremieredWork
chosen
Indicates that one entity is the composer who wrote a work that another entity premiered (first performed or presented).
-
B.
premieredWorkBy
Indicates that a creative work had its first public performance, showing, or presentation conducted by the specified entity.
-
C.
firstPerformanceWork
Indicates that a performance is the debut or initial presentation of a particular work.
-
D.
firstPerformanceBy
Indicates that the referenced performance is the earliest or debut performance carried out by the specified entity.
-
E.
premieredWorkType
Indicates the type or category of work (e.g., film, play, series) that was first premiered.
- 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_69f76e5c9b808190b486523f5c2f817d |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fcda3699948190adb57625bae08091 |
completed | May 7, 2026, 6:30 p.m. |
| PD | Predicate disambiguation | batch_69fcd8fd16d08190b0aca6e19a632e99 |
completed | May 7, 2026, 6:25 p.m. |
Created at: May 3, 2026, 4:31 p.m.