Triple
T23130698
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Symphony No. 5 (Peter Maxwell Davies) |
E577156
|
entity |
| Predicate | intendedGenreContext |
P82410
|
FINISHED |
| Object | concert music |
—
|
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: concert music | Statement: [Symphony No. 5 (Peter Maxwell Davies), intendedGenreContext, concert music]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: intendedGenreContext Context triple: [Symphony No. 5 (Peter Maxwell Davies), intendedGenreContext, concert music]
-
A.
genreContext
Indicates the contextual genre or categorical style associated with an entity, such as the thematic or stylistic framework in which it is situated.
-
B.
targetGenre
chosen
Indicates the genre that something is specifically aimed at, categorized under, or intended to belong to.
-
C.
usedGenre
Indicates that one entity employs or is associated with a particular genre in its creation, presentation, or classification.
-
D.
commonGenre
Indicates that two entities share at least one genre in common.
-
E.
genreWithin
Indicates that one genre is a subgenre or more specific category contained within another, broader genre.
- 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_69e245f7b0e481909c473ff4e6a54e2c |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f18e87cd188190b466f7a4c9670e56 |
completed | April 29, 2026, 4:52 a.m. |
| PD | Predicate disambiguation | batch_69ef89f83b108190aaaa1db6221fc163 |
completed | April 27, 2026, 4:08 p.m. |
Created at: April 17, 2026, 4 p.m.