Triple
T38590961
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Viera |
E932450
|
entity |
| Predicate | playableGenderLaterAddedInFFXIV |
P193175
|
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: [Viera, playableGenderLaterAddedInFFXIV, male]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: playableGenderLaterAddedInFFXIV Context triple: [Viera, playableGenderLaterAddedInFFXIV, male]
-
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.
protagonistGenderSelectable
Indicates that the gender of the story’s main character can be chosen or customized by the player or user.
-
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.
laterRecognizedGender
Indicates that an entity’s gender identity, as recognized or recorded at a later time, differs from or updates an earlier recorded gender.
- 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_69f76ec654d48190b421111cf26e54d9 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fd3d46d1f48190a1b20dd063224b7d |
completed | May 8, 2026, 1:32 a.m. |
| PD | Predicate disambiguation | batch_69fd3ae1510c81908fe1280efc17feee |
completed | May 8, 2026, 1:22 a.m. |
Created at: May 3, 2026, 4:32 p.m.