Triple
T2950081
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | On, Wisconsin! |
E79798
|
entity |
| Predicate | melodyType |
P44167
|
FINISHED |
| Object | marching band arrangement |
—
|
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: marching band arrangement | Statement: [On, Wisconsin!, melodyType, marching band arrangement]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: melodyType Context triple: [On, Wisconsin!, melodyType, marching band arrangement]
-
A.
hasMelody
Indicates that one entity possesses, contains, or is characterized by a particular melody.
-
B.
songType
Indicates the specific category or genre that a given song belongs to.
-
C.
melodyReusedBy
Indicates that a melody originally used in one work is later reused or incorporated in another work.
-
D.
melodyOrigin
Indicates the source or provenance from which a particular melody is derived or originally created.
-
E.
musicalMode
Indicates the specific tonal framework or scale system (mode) in which a piece of music or musical passage is organized.
- 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_69ad8b1276588190a374a0b12e0f7bdf |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad98f95da88190a036a18f39f221c2 |
completed | March 8, 2026, 3:42 p.m. |
| PD | Predicate disambiguation | batch_69ad960a70ac8190816b5ae3e8631031 |
completed | March 8, 2026, 3:30 p.m. |
| PDg | Predicate description generation | batch_69ad97f520208190a4dc43372004555f |
completed | March 8, 2026, 3:38 p.m. |
Created at: March 8, 2026, 2:57 p.m.