Triple
T33053205
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | I Vow to Thee, My Country |
E845782
|
entity |
| Predicate | dateOfMusicalSetting |
P6964
|
FINISHED |
| Object | 1921 |
—
|
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: 1921 | Statement: [I Vow to Thee, My Country, dateOfMusicalSetting, 1921]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dateOfMusicalSetting Context triple: [I Vow to Thee, My Country, dateOfMusicalSetting, 1921]
-
A.
musicalSettingMayBe
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.
musicDate
Indicates the date on which a piece of music was created, performed, released, or otherwise took place.
-
D.
dateOfComposition
chosen
Indicates the calendar date or time period when a particular work was created or composed.
-
E.
orchestrationDate
Indicates the date on which the orchestration (coordination or arrangement of related actions or processes) occurs or is scheduled to occur.
- 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_69f3495242e48190996a2cb2beab5455 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fcf1b3d9a08190850b388308656266 |
completed | May 7, 2026, 8:10 p.m. |
| PD | Predicate disambiguation | batch_69fcf0226d8c8190b23dceafb1794995 |
completed | May 7, 2026, 8:03 p.m. |
Created at: May 1, 2026, 1:24 a.m.