Triple
T29789969
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | E major |
E756375
|
entity |
| Predicate | concertPitchUsage |
P178809
|
FINISHED |
| Object | orchestral repertoire |
—
|
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: orchestral repertoire | Statement: [E major, concertPitchUsage, orchestral repertoire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: concertPitchUsage Context triple: [E major, concertPitchUsage, orchestral repertoire]
-
A.
musicUsed
Indicates that one entity makes use of or incorporates another entity as music, such as in a performance, production, or media context.
-
B.
hasPitch
Indicates that one entity possesses or is characterized by a specific pitch (such as a tonal, acoustic, or frequency-related property).
-
C.
usedAsInstrumentBy
Indicates that one entity functions as a tool, means, or instrument through which another entity performs an action or achieves an effect.
-
D.
relativePitch
Indicates a relationship where one entity’s pitch is defined or compared in terms of its interval or distance from another entity’s pitch.
-
E.
beatUsedIn
Indicates that a particular beat or rhythmic pattern is employed within a specific musical piece, section, or context.
- 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_69f22451fb748190bbdbab401280affb |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f71422adac8190a5ceb32dcf820833 |
completed | May 3, 2026, 9:23 a.m. |
| PD | Predicate disambiguation | batch_69f712764d2c819081b64b27e5de4a13 |
completed | May 3, 2026, 9:16 a.m. |
| PDg | Predicate description generation | batch_69f71421e8d08190807ccfb15d0f0ddb |
completed | May 3, 2026, 9:23 a.m. |
Created at: April 29, 2026, 5:12 p.m.