Triple
T23180867
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Old Shep |
E579456
|
entity |
| Predicate | ElvisPresleyFirstRecorded |
P38702
|
FINISHED |
| Object | 1956 |
—
|
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: 1956 | Statement: [Old Shep, ElvisPresleyFirstRecorded, 1956]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ElvisPresleyFirstRecorded Context triple: [Old Shep, ElvisPresleyFirstRecorded, 1956]
-
A.
ElvisPresleyVersionRecordedIn
Indicates that a particular version of a work or song, specifically Elvis Presley’s rendition, was recorded in a specified place or context.
-
B.
ElvisPresleyVersionReleaseYear
chosen
Indicates the year in which a particular version or release associated with Elvis Presley was issued.
-
C.
ElvisPresleyVersionAlbum
Indicates that an album is a version or edition associated with Elvis Presley’s recordings or releases.
-
D.
ElvisPresleyVersionBackedBy
Indicates that an Elvis Presley recording or rendition is musically supported or accompanied by the specified backing group, band, or arrangement.
-
E.
ElvisPresleyVersionLabel
Indicates that something is labeled or identified as the Elvis Presley version of a work or recording.
- 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_69e245ff8000819090d12008805315b7 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f18f6ebff48190ad1543051ca0239b |
completed | April 29, 2026, 4:56 a.m. |
| PD | Predicate disambiguation | batch_69ef8a041c0081909afb670d17a5aaba |
completed | April 27, 2026, 4:08 p.m. |
Created at: April 17, 2026, 4:05 p.m.