Triple
T37751840
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Viola Concerto in G major |
E940999
|
entity |
| Predicate | hasAlternativeArrangementsFor |
P197187
|
FINISHED |
| Object | cello |
—
|
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: cello | Statement: [Viola Concerto in G major, hasAlternativeArrangementsFor, cello]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAlternativeArrangementsFor Context triple: [Viola Concerto in G major, hasAlternativeArrangementsFor, cello]
-
A.
hasAlternativeArrangement
Indicates that one entity can be organized, configured, or structured in a different valid way as an alternative to its current or primary arrangement.
-
B.
hasMultipleArrangements
Indicates that an entity can exist or be configured in more than one distinct arrangement or setup.
-
C.
hasMusicalArrangementCharacteristic
Indicates that a musical arrangement possesses a specific characteristic, feature, or quality.
-
D.
hasAlternativeRadioVersionWith
Indicates that one audio track has a corresponding alternative version specifically edited or mixed for radio play.
-
E.
hasPianoArrangement
Indicates that one entity has a version or adaptation of it arranged specifically for piano.
- 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_69f76ee1f3a88190834e6c8af99bccc9 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fe7b1c506c8190869c1a22031e0571 |
completed | May 9, 2026, 12:09 a.m. |
| PD | Predicate disambiguation | batch_69fe796b2bdc8190a86980d44008f875 |
completed | May 9, 2026, 12:01 a.m. |
| PDg | Predicate description generation | batch_69fe7b1b3460819081172731b52ac15b |
completed | May 9, 2026, 12:08 a.m. |
Created at: May 3, 2026, 4:19 p.m.