Triple

T2507194
Position Surface form Disambiguated ID Type / Status
Subject Cöthen court E52611 entity
Predicate hasGenreSupported P30020 FINISHED
Object instrumental concerto LITERAL 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: instrumental concerto | Statement: [Cöthen court, hasGenreSupported, instrumental concerto]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasGenreSupported
Context triple: [Cöthen court, hasGenreSupported, instrumental concerto]
  • A. supportedGenre chosen
    Indicates that an entity (such as a system, service, or tool) is capable of handling, providing, or working with a specified genre.
  • B. hasGenreScope
    Indicates that something (such as a work, collection, or classification) is limited to, defined by, or applicable within a particular genre or set of genres.
  • C. hasSupported
    Indicates that one entity has provided assistance, endorsement, or backing to another entity, either materially, emotionally, or through advocacy.
  • D. hasTypeOfSupport
    Indicates that one entity provides or is associated with a particular kind or category of support in relation to another entity.
  • E. hasGenreInSeries
    Indicates that a particular genre is associated with, or applies to, a work as it appears within a specific series.
  • 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_69ab4958e76481908a235377dd921c9e completed March 6, 2026, 9:38 p.m.
NER Named-entity recognition batch_69abd65d6a988190aaaac8e98540a14f completed March 7, 2026, 7:40 a.m.
PD Predicate disambiguation batch_69abd0bd996c8190ba8b9d6e4333b8d4 completed March 7, 2026, 7:16 a.m.
Created at: March 6, 2026, 9:46 p.m.