Triple
T32114441
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Varda |
E820198
|
entity |
| Predicate | songMention |
P114550
|
FINISHED |
| Object | A Elbereth Gilthoniel |
—
|
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: A Elbereth Gilthoniel | Statement: [Varda, songMention, A Elbereth Gilthoniel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: songMention Context triple: [Varda, songMention, A Elbereth Gilthoniel]
-
A.
songAbout
Indicates that one entity (typically a song) has content, lyrics, or themes that are focused on, describe, or are dedicated to another entity.
-
B.
hasLyricsMentioning
chosen
Indicates that the referenced lyrics explicitly mention or refer to the specified entity.
-
C.
notableSongAssociations
Indicates that there are notable or significant associations between an entity and specific songs, such as being referenced by, inspiring, or otherwise prominently linked to those songs.
-
D.
notableLyricReference
Indicates that one entity contains a significant or well-known reference to the lyrics of another entity (such as a song or musical work).
-
E.
refersToSong
Indicates that one entity makes reference to, mentions, or is about a particular song.
- 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_69f3490209c881908ec0241476715f15 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b906a92c819096335394dd7f767e |
completed | May 3, 2026, 2:55 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a970b0819090c6473844ffa8e3 |
completed | May 3, 2026, 2:32 a.m. |
Created at: May 1, 2026, 12:28 a.m.