Triple
T20448522
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | I Wanna Be a Homosexual |
E501581
|
entity |
| Predicate | hasTargetOfCriticism |
P136764
|
FINISHED |
| Object | homophobic attitudes |
—
|
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: homophobic attitudes | Statement: [I Wanna Be a Homosexual, hasTargetOfCriticism, homophobic attitudes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTargetOfCriticism Context triple: [I Wanna Be a Homosexual, hasTargetOfCriticism, homophobic attitudes]
-
A.
hasCriticism
Indicates that one entity expresses disapproval, objection, or negative evaluation directed toward another entity.
-
B.
hasTargetOfCritique
chosen
Indicates that one entity is the object or focus of another entity’s criticism or evaluative critique.
-
C.
criticizedFor
Indicates that one entity expresses disapproval or negative judgment of another entity specifically because of a particular action, quality, or outcome.
-
D.
sometimesCriticizedFor
Indicates that an entity is on occasion the target of criticism for a particular reason, behavior, or attribute.
-
E.
aimsToCritique
Indicates an intention to analyze and point out faults, limitations, or weaknesses in something.
- 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_69e0b4ac0a1c81908845d0f8a56abce8 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e68cff1bcc8190bfc843686be117cb |
completed | April 20, 2026, 8:30 p.m. |
| PD | Predicate disambiguation | batch_69e57679eb40819086142df3e39c928e |
completed | April 20, 2026, 12:42 a.m. |
Created at: April 16, 2026, 11:32 a.m.