Triple
T30083755
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kingsfold |
E764542
|
entity |
| Predicate | hasNotableArrangementGenre |
P201705
|
FINISHED |
| Object | orchestral variations |
—
|
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: orchestral variations | Statement: [Kingsfold, hasNotableArrangementGenre, orchestral variations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableArrangementGenre Context triple: [Kingsfold, hasNotableArrangementGenre, orchestral variations]
-
A.
hasNotableGenre
Indicates that an entity is significantly associated with a particular genre, such that the genre is especially characteristic or noteworthy for that entity.
-
B.
hasNotableArrangementFor
Indicates that one entity is distinguished by a significant or noteworthy arrangement, configuration, or setup specifically made for another entity.
-
C.
hasNotableSongType
Indicates that an entity is associated with a specific type or category of notable song.
-
D.
hasNotableSubgenre
Indicates that one genre is recognized as a particularly significant or prominent subgenre of another genre.
-
E.
hasMainGenre
Indicates that an entity’s primary or most characteristic genre is the specified genre.
- F. None of above. chosen
Provenance (4 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_6a0017dd31d08190aa5e9f72df83733a |
completed | May 10, 2026, 5:30 a.m. |
| PD | Predicate disambiguation | batch_6a0015a1deb88190b9cdaa60455b0a33 |
completed | May 10, 2026, 5:20 a.m. |
| PDg | Predicate description generation | batch_6a0017dc2cd48190a89c3e9c71708519 |
completed | May 10, 2026, 5:30 a.m. |
Created at: April 29, 2026, 7:03 p.m.