Triple
T5463132
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mu isamaa, mu õnn ja rõõm |
E122641
|
entity |
| Predicate | adoptionAsNationalAnthemYear |
P14951
|
FINISHED |
| Object | 1920 |
—
|
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: 1920 | Statement: [Mu isamaa, mu õnn ja rõõm, adoptionAsNationalAnthemYear, 1920]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: adoptionAsNationalAnthemYear Context triple: [Mu isamaa, mu õnn ja rõõm, adoptionAsNationalAnthemYear, 1920]
-
A.
adoptedAsNationalAnthemYear
chosen
Indicates the year in which something was officially adopted as a national anthem.
-
B.
adoptedAsNationalAnthemInYear
Indicates that a song or musical composition was officially adopted as a country's national anthem in a specified year.
-
C.
reconfirmedAsNationalAnthemInYear
Indicates that something already designated as a national anthem was officially confirmed again in that role in a specified year.
-
D.
adoptedAsOfficialAnthemDate
Indicates the date on which something (typically a song or musical piece) was formally adopted as an official anthem.
-
E.
usedAsNationalAnthemUntil
Indicates that something served in the role of a national anthem up to a specified end time or date.
- 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_69bd4643f16081908d7f29e08096115a |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd927c946c8190aef40679199fede3 |
completed | March 20, 2026, 6:31 p.m. |
| PD | Predicate disambiguation | batch_69bd91a370a88190b5d17b8a5387138d |
completed | March 20, 2026, 6:27 p.m. |
Created at: March 20, 2026, 2:08 p.m.