Triple
T30083256
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brigg Fair |
E764529
|
entity |
| Predicate | notableOrchestralUseBy |
P207208
|
FINISHED |
| Object | Frederick Delius |
E318581
|
NE 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: Frederick Delius | Statement: [Brigg Fair, notableOrchestralUseBy, Frederick Delius]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableOrchestralUseBy Context triple: [Brigg Fair, notableOrchestralUseBy, Frederick Delius]
-
A.
isOrchestralWorkBy
Indicates that a particular orchestral work was created or composed by a specified composer or artist.
-
B.
notableInstrumentalContribution
Indicates that an entity has made a significant and influential instrumental contribution to another entity, work, or outcome.
-
C.
hasOrchestralScoreBy
Indicates that a musical work’s orchestral score was composed or arranged by a specified person or entity.
-
D.
notableWorkComposedWith
Indicates that a notable work was created using, in collaboration with, or through the involvement of a particular tool, medium, system, or co-creative entity.
-
E.
notableArrangementOf
Indicates that one entity is a significant or noteworthy configuration, ordering, or spatial organization of the other entity.
- F. None of above. chosen
Provenance (5 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_69f22473c0fc8190a926a8051b3b378b |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_6a037c9141dc819098d7fcc36e69882c |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a27892016348190a934b431f637fa9a |
completed | June 9, 2026, 3:31 a.m. |
| PD | Predicate disambiguation | batch_6a0379e0f3d88190a4ee7b0673f1ef90 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c7ee0388190a29faeb5cdb0950a |
completed | May 12, 2026, 7:16 p.m. |
Created at: April 29, 2026, 7:03 p.m.