Triple
T20060418
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | "Move, bitch, get out the way" |
E499455
|
entity |
| Predicate | hookType |
P138545
|
FINISHED |
| Object | call-and-response chant |
—
|
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: call-and-response chant | Statement: ["Move, bitch, get out the way", hookType, call-and-response chant]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hookType Context triple: ["Move, bitch, get out the way", hookType, call-and-response chant]
-
A.
hookOf
Indicates that one entity functions as a hook or hooking component that is part of, attached to, or used by another entity.
-
B.
hasHook
Indicates that one entity possesses, is equipped with, or features a hook in relation to another entity or context.
-
C.
hubType
Indicates the specific kind or category of hub associated with an entity or connection.
-
D.
hingeType
Indicates the specific kind or configuration of hinge mechanism that connects two parts or surfaces.
-
E.
hookPerformedBy
Indicates that a hook action or operation is carried out or executed by a particular agent or entity.
- 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_69da6276bcf48190aabbf279192a5fb4 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e66374f4a48190beb575a6c84ebdb4 |
completed | April 20, 2026, 5:33 p.m. |
| PD | Predicate disambiguation | batch_69e54cee7a5c819084ae4ff26419833f |
completed | April 19, 2026, 9:45 p.m. |
| PDg | Predicate description generation | batch_69e54fc20888819083c9118a09d0d2dc |
completed | April 19, 2026, 9:57 p.m. |
Created at: April 11, 2026, 3:38 p.m.