Triple
T26149540
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Swiss national anthem |
E659776
|
entity |
| Predicate | hasOfficialLyricsLanguage |
P11404
|
FINISHED |
| Object | Romansh |
—
|
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: Romansh | Statement: [Swiss national anthem, hasOfficialLyricsLanguage, Romansh]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOfficialLyricsLanguage Context triple: [Swiss national anthem, hasOfficialLyricsLanguage, Romansh]
-
A.
hasOfficialLyrics
Indicates that an entity (such as a song or musical work) has lyrics that are formally recognized or authorized as the official version.
-
B.
lyricsLanguage
chosen
Indicates the language in which the lyrics of a song or musical work are written or performed.
-
C.
hasUnofficialLyrics
Indicates that an entity is associated with lyrics that are not officially authorized or recognized by the original creator or rights holder.
-
D.
hasNoOfficialLyrics
Indicates that there are no formally released or officially recognized lyrics associated with the referenced work or piece.
-
E.
hasArtistLanguage
Indicates that an artist is associated with, or primarily uses, a particular language in their work or identity.
- 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_69ee5bc496a88190af7deb7ab5e081de |
completed | April 26, 2026, 6:39 p.m. |
| NER | Named-entity recognition | batch_69f6247480cc8190a887eedaeb94615c |
completed | May 2, 2026, 4:21 p.m. |
| PD | Predicate disambiguation | batch_69f623a7539c8190b71797f583da9f63 |
completed | May 2, 2026, 4:17 p.m. |
Created at: April 26, 2026, 8:24 p.m.