Triple
T2234186
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | State Anthem of the Soviet Union |
E49239
|
entity |
| Predicate | officialLyricsApproved |
P29645
|
FINISHED |
| Object | 1943 |
—
|
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: 1943 | Statement: [State Anthem of the Soviet Union, officialLyricsApproved, 1943]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: officialLyricsApproved Context triple: [State Anthem of the Soviet Union, officialLyricsApproved, 1943]
-
A.
hasOfficialLyrics
chosen
Indicates that an entity (such as a song or musical work) has lyrics that are formally recognized or authorized as the official version.
-
B.
hasUnofficialLyrics
Indicates that an entity is associated with lyrics that are not officially authorized or recognized by the original creator or rights holder.
-
C.
lyricsBy
Indicates that the lyrics of a song or musical work were written or authored by a specified person or entity.
-
D.
hasLyric
Indicates that one entity (typically a musical work or track) contains or is associated with the lyrics provided by another entity.
-
E.
hasLyricsSource
Indicates that one entity serves as the source or origin of the lyrics associated with another entity.
- 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_69a88aa84bdc819086df50e9c20b301e |
completed | March 4, 2026, 7:40 p.m. |
| NER | Named-entity recognition | batch_69abc09297a481909e8fe6ec645de616 |
completed | March 7, 2026, 6:07 a.m. |
| PD | Predicate disambiguation | batch_69abbdafc07881909101266a33ae7031 |
completed | March 7, 2026, 5:54 a.m. |
Created at: March 4, 2026, 7:47 p.m.