Triple
T11433996
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prey (2017 video game) |
E270957
|
entity |
| Predicate | protagonistGenderSelectable |
P99281
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Prey (2017 video game), protagonistGenderSelectable, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: protagonistGenderSelectable Context triple: [Prey (2017 video game), protagonistGenderSelectable, true]
-
A.
protagonistGenderIdentity
Indicates the gender identity attributed to or expressed by the protagonist in a given context.
-
B.
protagonistType
Indicates the role or category that the main character (protagonist) of a story or scenario belongs to.
-
C.
playsGender
Indicates that one entity performs or assumes a particular gender role or identity in a given context.
-
D.
hasMaleProtagonist
Indicates that the primary main character in the work is male.
-
E.
hasLeadCharacterGender
Indicates that the primary or lead character in a work has a specified gender.
- 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_69d6aadeef688190874bcecd88b3dd9b |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d806c485f481909dd3d9b0993f3faf |
completed | April 9, 2026, 8:06 p.m. |
| PD | Predicate disambiguation | batch_69d7e71436f88190ac7e45a04ea5c987 |
completed | April 9, 2026, 5:51 p.m. |
| PDg | Predicate description generation | batch_69d80010712c819089ea2e31e664abe1 |
completed | April 9, 2026, 7:37 p.m. |
Created at: April 8, 2026, 9:35 p.m.