Triple
T20106332
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thriller dance |
E490187
|
entity |
| Predicate | iconicOutfitAssociatedWithLead |
P128303
|
FINISHED |
| Object | red jacket |
—
|
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: red jacket | Statement: [Thriller dance, iconicOutfitAssociatedWithLead, red jacket]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: iconicOutfitAssociatedWithLead Context triple: [Thriller dance, iconicOutfitAssociatedWithLead, red jacket]
-
A.
personHasNotableStyle
Indicates that a person is recognized for having a distinctive or noteworthy style.
-
B.
typicallyWornBy
Indicates that something (such as an item or garment) is most commonly or characteristically worn by a particular type of person or group.
-
C.
notableOutfit
Indicates that an entity is known for or associated with wearing a particular outfit or style of clothing.
-
D.
oftenDepictedWearing
chosen
Indicates that an entity is frequently shown or represented as wearing a particular item or type of clothing in depictions or portrayals.
-
E.
hasInsigniaWornBy
Indicates that a particular insignia is worn by a specified entity (such as a person, group, or organization).
- 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_69da62636cc08190982cc71733a17b8d |
completed | April 11, 2026, 3:01 p.m. |
| NER | Named-entity recognition | batch_69e666dcb8d4819091889e19dd9137a6 |
completed | April 20, 2026, 5:48 p.m. |
| PD | Predicate disambiguation | batch_69e54cf788188190a46cc49c9ce7617f |
completed | April 19, 2026, 9:45 p.m. |
Created at: April 11, 2026, 11:28 p.m.