Triple
T31570590
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Symphony No. 3 |
E805546
|
entity |
| Predicate | hasRehearsalRequirement |
P203414
|
FINISHED |
| Object | multiple orchestral rehearsals |
—
|
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: multiple orchestral rehearsals | Statement: [Symphony No. 3, hasRehearsalRequirement, multiple orchestral rehearsals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRehearsalRequirement Context triple: [Symphony No. 3, hasRehearsalRequirement, multiple orchestral rehearsals]
-
A.
hasRehearsalSpaces
Indicates that an entity provides or contains designated spaces specifically intended for rehearsing activities or performances.
-
B.
hasRehearsalFormat
Indicates that an entity is associated with a particular format or structure in which a rehearsal is conducted.
-
C.
requiresPractice
Indicates that performing or mastering one entity depends on engaging in repeated practice or training involving another entity.
-
D.
hasRecitalsCount
Indicates the number of recitals associated with a given entity.
-
E.
hasImprovisationFrom
Indicates that something includes or is derived from an improvisational performance or source.
- 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_69f348d2ee94819091918d1789398c29 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_6a017969ff908190a7a1a46b3f5ae362 |
completed | May 11, 2026, 6:38 a.m. |
| PD | Predicate disambiguation | batch_6a017609ff4c8190aba8a1864d39a608 |
completed | May 11, 2026, 6:24 a.m. |
| PDg | Predicate description generation | batch_6a01796929088190a09c990c6b4a312c |
completed | May 11, 2026, 6:38 a.m. |
Created at: April 30, 2026, 10:19 p.m.