Triple
T23566672
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Elvis Presley’s 1969 Las Vegas engagement |
E579389
|
entity |
| Predicate | setListIncluded |
P63353
|
FINISHED |
| Object | Blue Suede Shoes |
—
|
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: Blue Suede Shoes | Statement: [Elvis Presley’s 1969 Las Vegas engagement, setListIncluded, Blue Suede Shoes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: setListIncluded Context triple: [Elvis Presley’s 1969 Las Vegas engagement, setListIncluded, Blue Suede Shoes]
-
A.
includesList
chosen
Indicates that one entity contains or encompasses a specified list of other entities as its elements or members.
-
B.
initiallyIncluded
Indicates that an entity was part of a specified set, group, or configuration at the beginning of a process, period, or state.
-
C.
includesListedOn
Indicates that one entity contains or references another entity that is recorded or displayed on a specific list or listing.
-
D.
hasIncluded
Indicates that one entity has incorporated or contained another entity as part of itself or within its scope.
-
E.
includedWith
Indicates that one entity is provided or packaged together as part of another entity.
- 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_69e245fe24588190888f3aec8407d8e3 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f1af6d3dcc8190bb127632e101a053 |
completed | April 29, 2026, 7:12 a.m. |
| PD | Predicate disambiguation | batch_69f118bcc0b08190b25a8dddfd461a0e |
completed | April 28, 2026, 8:29 p.m. |
Created at: April 17, 2026, 6:35 p.m.