Triple
T4080172
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | On, Brave Old Army Team |
E87457
|
entity |
| Predicate | melodyUsedBy |
P4543
|
FINISHED |
| Object | United States Military Academy Band arrangements |
—
|
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: United States Military Academy Band arrangements | Statement: [On, Brave Old Army Team, melodyUsedBy, United States Military Academy Band arrangements]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: melodyUsedBy Context triple: [On, Brave Old Army Team, melodyUsedBy, United States Military Academy Band arrangements]
-
A.
melodyReusedBy
Indicates that a melody originally used in one work is later reused or incorporated in another work.
-
B.
melodyType
Indicates the specific kind or category of melody associated with or used by an entity.
-
C.
hasMelody
chosen
Indicates that one entity possesses, contains, or is characterized by a particular melody.
-
D.
melodyOrigin
Indicates the source or provenance from which a particular melody is derived or originally created.
-
E.
isEarlierUseOfMelodyThan
Indicates that one use of a melody occurs at an earlier time than another use of the same or comparable melody.
- 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_69aed9435cf48190ad1da737c962d19d |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefc5087b081909d6042bfe8d8a306 |
completed | March 9, 2026, 4:58 p.m. |
| PD | Predicate disambiguation | batch_69aef9082c2081908474f082a49bebc8 |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:39 p.m.