Triple
T16810365
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Hulkster |
E408591
|
entity |
| Predicate | hasAssociatedGesture |
P124947
|
FINISHED |
| Object | ear-cupping taunt |
—
|
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: ear-cupping taunt | Statement: [The Hulkster, hasAssociatedGesture, ear-cupping taunt]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAssociatedGesture Context triple: [The Hulkster, hasAssociatedGesture, ear-cupping taunt]
-
A.
hasTouchControls
Indicates that an entity supports or is operated through touch-based input controls.
-
B.
hasStylus
Indicates that an entity possesses or is equipped with a stylus as an accessory or tool.
-
C.
hasChoreographer
Indicates that one entity serves as the choreographer responsible for designing or directing the movement or dance for another entity.
-
D.
hasGripType
Indicates that one entity possesses or uses a specific type or style of grip in relation to another entity or action.
-
E.
hasAssociatedPosition
Indicates that one entity is linked to a specific role, job, or spatial/organizational position associated with it.
- F. None of above. chosen
Provenance (4 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_69d88393905081908d00a86b99996ac8 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3b2cf680c8190bcd640570c524918 |
completed | April 18, 2026, 4:35 p.m. |
| PD | Predicate disambiguation | batch_69e32b814b188190aee525f8779203cd |
completed | April 18, 2026, 6:58 a.m. |
| PDg | Predicate description generation | batch_69e34fb7c8c8819086975b7955b7d8ef |
completed | April 18, 2026, 9:32 a.m. |
Created at: April 10, 2026, 5:23 a.m.