Triple
T33125857
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | I Hear an Army |
E847720
|
entity |
| Predicate | musicalSettingTitle |
P169933
|
FINISHED |
| Object | Three Songs, Op. 10 |
—
|
NE NERFINISHED |
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: Three Songs, Op. 10 | Statement: [I Hear an Army, musicalSettingTitle, Three Songs, Op. 10]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: musicalSettingTitle Context triple: [I Hear an Army, musicalSettingTitle, Three Songs, Op. 10]
-
A.
musicalSettingMayBe
chosen
Indicates that one entity can serve as a musical setting or arrangement for another (such as a text, work, or performance context).
-
B.
notableMusicalSetting
Indicates that a work or text has been set to music in a particularly significant, recognized, or influential way.
-
C.
settingInMusical
Indicates that one entity serves as the setting or location in which the events of a musical take place.
-
D.
sourceMusicalTitle
Indicates that one musical work is derived from, based on, or uses material from another specified musical title.
-
E.
incidentalMusicTitle
Indicates that a work serves as incidental music for another work and specifies the title of that associated 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_69f349588f088190b7c9588860f72033 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fd4f39b5008190b83b3227ce22c509 |
completed | May 8, 2026, 2:49 a.m. |
| PD | Predicate disambiguation | batch_69fd4df17c548190a4e2a6fea70f7e10 |
completed | May 8, 2026, 2:44 a.m. |
Created at: May 1, 2026, 1:27 a.m.