Triple
T13107608
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hot Butterfly |
E310883
|
entity |
| Predicate | hasAdultContent |
P47549
|
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: [Hot Butterfly, hasAdultContent, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAdultContent Context triple: [Hot Butterfly, hasAdultContent, true]
-
A.
containsAdultContent
chosen
Indicates that the referenced item includes material intended for adults, such as explicit sexual, violent, or otherwise age-restricted content.
-
B.
hasAdultRank
Indicates that an entity holds a status or position classified as an adult-level rank within a given system or hierarchy.
-
C.
hasContentRating
Indicates that something is associated with a specified content rating that reflects its suitability for particular audiences.
-
D.
hasAdultPrograms
Indicates that an entity offers or is associated with programs or services specifically designed for adults.
-
E.
isAdultCharacter
Indicates that a character has reached adulthood, typically meeting the age or maturity criteria defining an adult within the given context.
- 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_69d806a872d08190a329806f8ff30df4 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d9817ce07881909ec552bf861ac175 |
completed | April 10, 2026, 11:02 p.m. |
| PD | Predicate disambiguation | batch_69d98041a3548190a05ddd83dbb660fa |
completed | April 10, 2026, 10:57 p.m. |
Created at: April 9, 2026, 9:05 p.m.