Triple
T20311563
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | I Sang Dixie |
E510260
|
entity |
| Predicate | lyricalElement |
P41008
|
FINISHED |
| Object | reference to Dixie |
—
|
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: reference to Dixie | Statement: [I Sang Dixie, lyricalElement, reference to Dixie]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lyricalElement Context triple: [I Sang Dixie, lyricalElement, reference to Dixie]
-
A.
lyricalEvent
Indicates an event or occurrence that is expressed, referenced, or described within the lyrics of a song.
-
B.
lyricalPhrase
chosen
Indicates that one entity is a lyrical phrase or line that is part of, derived from, or associated with another entity such as a song, poem, or musical work.
-
C.
lyricalFunction
Indicates the role or purpose that lyrics serve within a musical or poetic work, such as narrating, expressing emotion, or structuring the piece.
-
D.
lyricalDevice
Indicates the use of a specific poetic or musical technique within lyrics to achieve a particular expressive or aesthetic effect.
-
E.
hasLyricalForm
Indicates that one entity (typically a musical or poetic work) possesses or is characterized by a particular lyrical structure or form.
- 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_69e0b4c7491c8190961113c4283b10b0 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e677441f9c8190acf98dc92c77732b |
completed | April 20, 2026, 6:58 p.m. |
| PD | Predicate disambiguation | batch_69e55b21b09081909e46691b6f45a07f |
completed | April 19, 2026, 10:45 p.m. |
Created at: April 16, 2026, 11:19 a.m.