Triple
T6268501
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1968 Comeback Special |
E140471
|
entity |
| Predicate | costumeHighlight |
P58290
|
FINISHED |
| Object | black leather outfit worn by Elvis Presley |
—
|
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: black leather outfit worn by Elvis Presley | Statement: [1968 Comeback Special, costumeHighlight, black leather outfit worn by Elvis Presley]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: costumeHighlight Context triple: [1968 Comeback Special, costumeHighlight, black leather outfit worn by Elvis Presley]
-
A.
costumeFeatures
chosen
Indicates that a costume possesses or includes specific features, attributes, or decorative elements.
-
B.
costume
Indicates that one entity is wearing, dressed in, or outfitted with the other entity as a costume.
-
C.
costumeElement
Indicates that one item functions as a component or part of another item's costume.
-
D.
costumeType
Indicates the specific kind or category of costume associated with an entity.
-
E.
costumeDesignNotability
Indicates that an entity is notable or recognized specifically for its work or achievements in costume design.
- 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_69c008cabc4081909723e2547c9d6cc0 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c063a28da081909f4bec8f7c1dedef |
completed | March 22, 2026, 9:48 p.m. |
| PD | Predicate disambiguation | batch_69c05606fb50819082d1a5a91e5030b6 |
completed | March 22, 2026, 8:50 p.m. |
Created at: March 22, 2026, 4:25 p.m.