Triple
T22957752
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Choir Boy |
E570807
|
entity |
| Predicate | protagonistGenderIdentityTheme |
P150380
|
FINISHED |
| Object | gender identity |
—
|
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: gender identity | Statement: [Choir Boy, protagonistGenderIdentityTheme, gender identity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: protagonistGenderIdentityTheme Context triple: [Choir Boy, protagonistGenderIdentityTheme, gender identity]
-
A.
protagonistGenderIdentity
Indicates the gender identity attributed to or expressed by the protagonist in a given context.
-
B.
protagonistGenderSelectable
Indicates that the gender of the story’s main character can be chosen or customized by the player or user.
-
C.
protagonistType
Indicates the role or category that the main character (protagonist) of a story or scenario belongs to.
-
D.
hasCrossDressingProtagonist
Indicates that the main character in the work regularly dresses in clothing traditionally associated with another gender.
-
E.
protagonistIs
Indicates that one entity serves as the main character or central figure in relation to another entity or narrative context.
- 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_69e245b212a88190b5259caf51606084 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f181f21e588190a5a88a15c1b55dea |
completed | April 29, 2026, 3:58 a.m. |
| PD | Predicate disambiguation | batch_69ef3b882e708190b0eb0c87021c75b8 |
completed | April 27, 2026, 10:33 a.m. |
| PDg | Predicate description generation | batch_69ef538a115081908982597f79355840 |
completed | April 27, 2026, 12:16 p.m. |
Created at: April 17, 2026, 3:47 p.m.