Triple
T20740642
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Finding Graceland |
E510428
|
entity |
| Predicate | hasElvisRelatedContent |
P141326
|
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: [Finding Graceland, hasElvisRelatedContent, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasElvisRelatedContent Context triple: [Finding Graceland, hasElvisRelatedContent, true]
-
A.
ElvisPresleyVersionLabel
Indicates that something is labeled or identified as the Elvis Presley version of a work or recording.
-
B.
ElvisPresleyVersionBackedBy
Indicates that an Elvis Presley recording or rendition is musically supported or accompanied by the specified backing group, band, or arrangement.
-
C.
ElvisPresleyVersionAlbum
Indicates that an album is a version or edition associated with Elvis Presley’s recordings or releases.
-
D.
ElvisPresleyVersionReleaseYear
Indicates the year in which a particular version or release associated with Elvis Presley was issued.
-
E.
hasSongAbout
Indicates that one entity has created, features, or is associated with a song whose subject or theme is about another entity.
- 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_69e0b4c845e88190b4c5f3ae79291182 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c20e76ac8190985203b2c17aca14 |
completed | April 21, 2026, 12:17 a.m. |
| PD | Predicate disambiguation | batch_69e5c0509608819080cdbf47fcddfe36 |
completed | April 20, 2026, 5:57 a.m. |
| PDg | Predicate description generation | batch_69e5c3cbe5788190b7ace43bfdac2ef6 |
completed | April 20, 2026, 6:12 a.m. |
Created at: April 16, 2026, 12:32 p.m.