Triple
T17249956
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | We Luv Deez Hoez |
E418724
|
entity |
| Predicate | hasProvocativeTitle |
P126710
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [We Luv Deez Hoez, hasProvocativeTitle, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasProvocativeTitle Context triple: [We Luv Deez Hoez, hasProvocativeTitle, true]
-
A.
hasTitlePun
Indicates that an entity’s title involves a pun or wordplay, typically combining multiple meanings or sounds for humorous or clever effect.
-
B.
hasTitleIn
Indicates that an entity holds or is associated with a specific title within a particular context, domain, or language.
-
C.
usesTitle
Indicates that one entity refers to or addresses another entity using a specific title or formal designation.
-
D.
hasTitleSubject
Indicates that an entity has a specific subject or topic as the focus of its title.
-
E.
mayBeTitled
Indicates that an entity can optionally bear or be assigned a particular title, but is not required to have 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_69d886d9ab108190b70edd8d17aa1204 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e42e2636f48190b29548ff80402bef |
completed | April 19, 2026, 1:21 a.m. |
| PD | Predicate disambiguation | batch_69e3832a284481908a8a3da7ac91de5a |
completed | April 18, 2026, 1:12 p.m. |
| PDg | Predicate description generation | batch_69e39c2fedb881908bfed2c3e5f2616a |
completed | April 18, 2026, 2:58 p.m. |
Created at: April 10, 2026, 5:39 a.m.