Triple
T37414460
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hallé Youth Orchestra |
E929660
|
entity |
| Predicate | rehearsalFrequency |
P2557
|
FINISHED |
| Object | weekly during term time |
—
|
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: weekly during term time | Statement: [Hallé Youth Orchestra, rehearsalFrequency, weekly during term time]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rehearsalFrequency Context triple: [Hallé Youth Orchestra, rehearsalFrequency, weekly during term time]
-
A.
performedFrequency
Indicates how often an action or activity is carried out within a given time period.
-
B.
hasRehearsalSpaces
Indicates that an entity provides or contains designated spaces specifically intended for rehearsing activities or performances.
-
C.
frequentPerformance
Indicates that an entity regularly or repeatedly carries out a particular performance or activity over a period of time.
-
D.
replayFrequency
Indicates how often an event, action, or sequence is repeated or played back over a given period.
-
E.
meetingFrequency
chosen
Indicates how often a meeting or recurring gathering takes place over a given period.
- 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_69f76ebde49481908566cd96b37ccc84 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fb9e1845e881908d19158440cf3b87 |
completed | May 6, 2026, 8:01 p.m. |
| PD | Predicate disambiguation | batch_69fb8d08d6988190a00794ac26078348 |
completed | May 6, 2026, 6:48 p.m. |
Created at: May 3, 2026, 4:16 p.m.