Triple
T2187775
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Richard Pryor: Live in Concert |
E49189
|
entity |
| Predicate | containsProfanity |
P37187
|
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: [Richard Pryor: Live in Concert, containsProfanity, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsProfanity Context triple: [Richard Pryor: Live in Concert, containsProfanity, true]
-
A.
hasNotableWord
Indicates that an entity is associated with a word or term that is considered notable, distinctive, or significant in some context.
-
B.
containsOathBy
Indicates that one entity (such as a text, document, or statement) includes or features an oath made by another entity.
-
C.
containsContaminant
Indicates that one entity includes, holds, or is tainted by an unwanted or harmful contaminating substance or element.
-
D.
usesInclusiveLanguage
Indicates that the subject communicates in a way that avoids biased, exclusionary, or discriminatory language toward any group.
-
E.
canCensure
Indicates that one entity has the authority or power to formally reprimand, criticize, or express disapproval of another entity’s actions or behavior.
- 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_69a88aa72d348190a9544bb5b8a4e71d |
completed | March 4, 2026, 7:40 p.m. |
| NER | Named-entity recognition | batch_69abbf9e99f08190892d34485c8f2f25 |
completed | March 7, 2026, 6:03 a.m. |
| PD | Predicate disambiguation | batch_69abbda32d1881909d1fd83a751fb21c |
completed | March 7, 2026, 5:54 a.m. |
| PDg | Predicate description generation | batch_69abbf9c77fc8190a323bcaf644fb2c5 |
completed | March 7, 2026, 6:03 a.m. |
Created at: March 4, 2026, 7:45 p.m.