Triple
T35394557
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mama |
E1023035
|
entity |
| Predicate | hasPlayableGender |
P193175
|
FINISHED |
| Object | female |
—
|
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: female | Statement: [Mama, hasPlayableGender, female]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPlayableGender Context triple: [Mama, hasPlayableGender, female]
-
A.
playableGender
chosen
Indicates that a particular gender is available as a selectable option for a player character.
-
B.
playsGender
Indicates that one entity performs or assumes a particular gender role or identity in a given context.
-
C.
hasPlayableCharacter
Indicates that an entity includes or is associated with a character that a user can control or play as.
-
D.
hasGenderRole
Indicates that an entity is associated with, or expected to perform, a particular socially defined gender-based role or set of behaviors.
-
E.
eligiblePlayersGender
Indicates that the relationship specifies which player genders are allowed or considered eligible 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_69f76df34ba48190bd80f0814cdcd540 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fd8ccbd4c88190b13aae0673b3c821 |
completed | May 8, 2026, 7:12 a.m. |
| PD | Predicate disambiguation | batch_69fd8ae2227c819089546f5c3629799e |
completed | May 8, 2026, 7:04 a.m. |
Created at: May 3, 2026, 4:03 p.m.