Triple
T20193077
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pokémon Ruby and Sapphire |
E493018
|
entity |
| Predicate | playerCharacterGenderChoice |
P99281
|
FINISHED |
| Object | male |
—
|
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 | Statement: [Pokémon Ruby and Sapphire, playerCharacterGenderChoice, male]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: playerCharacterGenderChoice Context triple: [Pokémon Ruby and Sapphire, playerCharacterGenderChoice, male]
-
A.
protagonistGenderSelectable
chosen
Indicates that the gender of the story’s main character can be chosen or customized by the player or user.
-
B.
playsGender
Indicates that one entity performs or assumes a particular gender role or identity in a given context.
-
C.
characterSelection
Indicates the relationship where a user or system chooses one or more characters from a set of available options.
-
D.
genderCustom
Indicates that an entity has a user-specified or non-standard gender designation beyond predefined gender categories.
-
E.
protagonistGenderIdentity
Indicates the gender identity attributed to or expressed by the protagonist 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_69da6268a034819081cbd9ea5a1c9475 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e66ad7270081908ed8513a8363e9b1 |
completed | April 20, 2026, 6:05 p.m. |
| PD | Predicate disambiguation | batch_69e55b11124c8190babacf2a0fe2d057 |
completed | April 19, 2026, 10:45 p.m. |
Created at: April 11, 2026, 11:37 p.m.