Triple
T5665248
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal Decree 1560/1997 |
E124842
|
entity |
| Predicate | hasNoOfficialLyrics |
P65624
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Royal Decree 1560/1997, hasNoOfficialLyrics, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNoOfficialLyrics Context triple: [Royal Decree 1560/1997, hasNoOfficialLyrics, true]
-
A.
hasUnofficialLyrics
Indicates that an entity is associated with lyrics that are not officially authorized or recognized by the original creator or rights holder.
-
B.
hasNoLyrics
Indicates that the referenced musical work or audio track does not contain any sung or spoken lyrics.
-
C.
hasOfficialLyrics
Indicates that an entity (such as a song or musical work) has lyrics that are formally recognized or authorized as the official version.
-
D.
hasLyric
Indicates that one entity (typically a musical work or track) contains or is associated with the lyrics provided by another entity.
-
E.
hasUnknownLyricist
Indicates that the lyricist associated with a work is not known or cannot be identified.
- F. None of above. chosen
Provenance (4 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_69c00828906881908966f270b8f130cf |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c0236d3f94819095111c41a323612d |
completed | March 22, 2026, 5:14 p.m. |
| PD | Predicate disambiguation | batch_69c021ba4ec481909db8cdbf0e907dd6 |
completed | March 22, 2026, 5:07 p.m. |
| PDg | Predicate description generation | batch_69c0236af5308190b3d698eadf7bcd2b |
completed | March 22, 2026, 5:14 p.m. |
Created at: March 22, 2026, 3:43 p.m.