Triple
T13509242
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | May Week |
E321092
|
entity |
| Predicate | currentTimingNote |
P86020
|
FINISHED |
| Object | now held in June despite the name |
—
|
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: now held in June despite the name | Statement: [May Week, currentTimingNote, now held in June despite the name]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: currentTimingNote Context triple: [May Week, currentTimingNote, now held in June despite the name]
-
A.
currentLengthNote
Indicates that an entity’s presently measured or recorded length is being noted or specified.
-
B.
startTimeNote
chosen
Indicates the specific time-related note or annotation associated with when an event or action begins.
-
C.
timeSignatureChange
Indicates a change from one musical time signature to another within a piece or passage.
-
D.
hasTempoMarking
Indicates that a musical passage, piece, or event is associated with a specific tempo indication or marking.
-
E.
tempo
Indicates the speed or pace at which an action, process, or sequence unfolds over time.
- 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_69d807629d6c8190998f1b9bb12d2ed0 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbaf85a74081909eb08751fc55ce8f |
completed | April 12, 2026, 2:43 p.m. |
| PD | Predicate disambiguation | batch_69dbae0b63748190b5e207f84b2532ea |
completed | April 12, 2026, 2:36 p.m. |
Created at: April 9, 2026, 9:43 p.m.