Triple
T31351921
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Best at It |
E799615
|
entity |
| Predicate | hasLGBTQContent |
P45364
|
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: [The Best at It, hasLGBTQContent, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLGBTQContent Context triple: [The Best at It, hasLGBTQContent, yes]
-
A.
hasLGBTTheme
chosen
Indicates that the subject includes, features, or centrally involves lesbian, gay, bisexual, or transgender themes or issues.
-
B.
hasLGBTCharacter
Indicates that the subject includes, features, or is associated with one or more characters who identify as lesbian, gay, bisexual, or transgender.
-
C.
containsAdultContent
Indicates that the referenced item includes material intended for adults, such as explicit sexual, violent, or otherwise age-restricted content.
-
D.
isOpenlyLGBT
Indicates that an entity publicly identifies as lesbian, gay, bisexual, transgender, or otherwise part of the LGBT community.
-
E.
hasLGBTParents
Indicates that an individual has one or more parents who identify as lesbian, gay, bisexual, or transgender.
- 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_69f224e5e9bc8190a16339328897c4f8 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69f41de8881909aaa06c49e89a022 |
completed | May 3, 2026, 1:05 a.m. |
| PD | Predicate disambiguation | batch_69f69d1d25e88190a7f57d323574da90 |
completed | May 3, 2026, 12:55 a.m. |
Created at: April 29, 2026, 9:17 p.m.