Triple
T30421496
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ashley Graham |
E773912
|
entity |
| Predicate | playableCharacterInSection |
P43877
|
FINISHED |
| Object | Resident Evil 4 (2005) |
—
|
NE NERFINISHED |
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: Resident Evil 4 (2005) | Statement: [Ashley Graham, playableCharacterInSection, Resident Evil 4 (2005)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: playableCharacterInSection Context triple: [Ashley Graham, playableCharacterInSection, Resident Evil 4 (2005)]
-
A.
hasPlayableCharacter
chosen
Indicates that an entity includes or is associated with a character that a user can control or play as.
-
B.
playableCharacterFormOf
Indicates that one entity is a specific form or version of another entity as it appears as a playable character.
-
C.
screenCharacterBy
Indicates a relationship where one entity evaluates or selects characters according to certain criteria or standards.
-
D.
playableInGame
Indicates that something can be used or controlled as an active element within a particular game.
-
E.
characterInPlayBy
Indicates that a character appears in or is part of a play authored or created by a specific person.
- 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_69f22491ba248190b9a4776ca8e42d02 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f68663d49c81908c44b8cb0f31d014 |
completed | May 2, 2026, 11:19 p.m. |
| PD | Predicate disambiguation | batch_69f678d019fc8190913662cd2f87b857 |
completed | May 2, 2026, 10:21 p.m. |
Created at: April 29, 2026, 8:06 p.m.