Triple
T2436999
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coronation of George II |
E52982
|
entity |
| Predicate | usedMusicFor |
P33428
|
FINISHED |
| Object | processional sections |
—
|
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: processional sections | Statement: [Coronation of George II, usedMusicFor, processional sections]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedMusicFor Context triple: [Coronation of George II, usedMusicFor, processional sections]
-
A.
usedFor
Indicates that one entity serves a purpose, function, or role in accomplishing, enabling, or supporting another entity or activity.
-
B.
usesMusicEnsemble
chosen
Indicates that one entity employs or incorporates a particular music ensemble in carrying out an action, function, or production.
-
C.
usesInstrument
Indicates that an agent performs an action by employing a specific instrument or tool as the means to carry it out.
-
D.
usedDuring
Indicates that one entity is employed, applied, or active in the course of another entity’s process, event, or time period.
-
E.
musicContribution
Indicates that an entity has contributed in some way to the creation, performance, or production of a musical work.
- 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_69ab4959bcc0819083246f9fb10439e3 |
completed | March 6, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69abcebf7cac8190889e6890d72c256c |
completed | March 7, 2026, 7:07 a.m. |
| PD | Predicate disambiguation | batch_69abc5ac11b081908ce6a506e81a742a |
completed | March 7, 2026, 6:29 a.m. |
Created at: March 6, 2026, 9:43 p.m.