Triple
T30007182
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Joe Dirt 2: Beautiful Loser |
E762356
|
entity |
| Predicate | featuresHairStyle |
P95511
|
FINISHED |
| Object | mullet-wearing protagonist |
—
|
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: mullet-wearing protagonist | Statement: [Joe Dirt 2: Beautiful Loser, featuresHairStyle, mullet-wearing protagonist]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresHairStyle Context triple: [Joe Dirt 2: Beautiful Loser, featuresHairStyle, mullet-wearing protagonist]
-
A.
hairType
Indicates the specific kind or category of hair an entity has, such as its texture, style, or structural type.
-
B.
hairStyleLater
Indicates that one entity’s hairstyle occurs or is observed at a later time than another entity’s hairstyle.
-
C.
hairStyleInMedia
chosen
Indicates that a particular hairstyle is depicted or represented in a specific media work or context.
-
D.
hasHair
Indicates that an entity possesses hair as a physical attribute.
-
E.
hairStyleForRole
Indicates that a particular hairstyle is designated or used for a specific role or character.
- 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_69f2246a47ac81909cf5213053687ffc |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69ffbe9e47688190a2692566dc326646 |
completed | May 9, 2026, 11:09 p.m. |
| PD | Predicate disambiguation | batch_69ffbb7b45388190b62cbde5c2d435cd |
completed | May 9, 2026, 10:55 p.m. |
Created at: April 29, 2026, 6:43 p.m.