Triple
T15466463
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Electrodrome |
E372041
|
entity |
| Predicate | musicBehavior |
P11860
|
FINISHED |
| Object | music changes intensity during the race |
—
|
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: music changes intensity during the race | Statement: [Electrodrome, musicBehavior, music changes intensity during the race]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: musicBehavior Context triple: [Electrodrome, musicBehavior, music changes intensity during the race]
-
A.
songBehavior
Indicates how an entity typically performs, uses, or interacts with a song in a given context.
-
B.
musicActivity
Indicates involvement in an activity related to creating, performing, practicing, or engaging with music.
-
C.
musicMovement
Indicates a relationship where a musical work, performance, or composition is associated with a specific movement or section within a larger musical piece.
-
D.
musicalMode
Indicates the specific tonal framework or scale system (mode) in which a piece of music or musical passage is organized.
-
E.
musicDriven
chosen
Indicates that one entity’s behavior, structure, or progression is guided, influenced, or determined primarily by music or musical elements.
- 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_69d85cc8bd308190886949510b42e764 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e03f680cec8190836a5ec841dee224 |
completed | April 16, 2026, 1:46 a.m. |
| PD | Predicate disambiguation | batch_69ded284bd008190b31c53b4f1cebadd |
completed | April 14, 2026, 11:49 p.m. |
Created at: April 10, 2026, 3:33 a.m.