Triple
T36312683
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | /x/ |
E894103
|
entity |
| Predicate | nsfwContentAllowed |
P148847
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [/x/, nsfwContentAllowed, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nsfwContentAllowed Context triple: [/x/, nsfwContentAllowed, yes]
-
A.
hasNSFWPolicy
Indicates that an entity has an established policy governing the handling, display, or treatment of not-safe-for-work (NSFW) content.
-
B.
containsAdultContent
Indicates that the referenced item includes material intended for adults, such as explicit sexual, violent, or otherwise age-restricted content.
-
C.
allowedContent
chosen
Indicates that certain content is permitted or acceptable within a given context, policy, or system.
-
D.
hasContentRating
Indicates that something is associated with a specified content rating that reflects its suitability for particular audiences.
-
E.
contentRestriction
Indicates that access to or use of certain content is limited or controlled based on specified rules or conditions.
- 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_69f76e4c1b248190b10667d0213537fe |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7ba6d06f48190a71b5a2f19e2232f |
completed | May 3, 2026, 9:13 p.m. |
| PD | Predicate disambiguation | batch_69f7b9a4aad48190a62e41c5e39339d9 |
completed | May 3, 2026, 9:09 p.m. |
Created at: May 3, 2026, 4:09 p.m.