Triple
T30017878
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Ballad of Little Jo |
E762644
|
entity |
| Predicate | protagonistGenderPresentation |
P73491
|
FINISHED |
| Object | male disguise |
—
|
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: male disguise | Statement: [The Ballad of Little Jo, protagonistGenderPresentation, male disguise]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: protagonistGenderPresentation Context triple: [The Ballad of Little Jo, protagonistGenderPresentation, male disguise]
-
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.
protagonistGenderIdentityTheme
Indicates that the work explores themes related to the protagonist’s gender identity and its development, expression, or impact within the narrative.
-
D.
genderOfPersona
Indicates the gender identity associated with a given persona.
-
E.
playsGender
chosen
Indicates that one entity performs or assumes a particular gender role or identity in a 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_69f2246b0c84819094f1250b6a02d277 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f6a916d2e08190bafc01cba73b6469 |
completed | May 3, 2026, 1:47 a.m. |
| PD | Predicate disambiguation | batch_69f6a7548eb48190a69b60a3c6ad53b9 |
completed | May 3, 2026, 1:39 a.m. |
Created at: April 29, 2026, 6:46 p.m.