Triple
T29161421
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | So F**king Rock |
E739197
|
entity |
| Predicate | containsExplicitLanguage |
P168921
|
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: [So F**king Rock, containsExplicitLanguage, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsExplicitLanguage Context triple: [So F**king Rock, containsExplicitLanguage, true]
-
A.
hasExplicitLanguage
chosen
Indicates that the subject contains or uses language that is coarse, profane, or otherwise unsuitable for certain audiences.
-
B.
includesLanguage
Indicates that one entity contains, supports, or makes use of a specified language as part of its content, functionality, or representation.
-
C.
hasSignificantLanguage
Indicates that an entity possesses a language that plays an important or primary role in its communication, identity, or functioning.
-
D.
hasLanguageInCountry
Indicates that a particular language is used or recognized within a specified country.
-
E.
hasLanguageOn
Indicates that an entity uses or is associated with a particular language in a specific context, medium, or location.
- 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_69f07cb528fc8190a556b73990c347c8 |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69fe349879848190bcd77e3cc3470458 |
completed | May 8, 2026, 7:08 p.m. |
| PD | Predicate disambiguation | batch_69fe31e3cf908190b23ebc2f7fe58722 |
completed | May 8, 2026, 6:56 p.m. |
Created at: April 28, 2026, 11:48 a.m.