Triple
T2433176
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dishonored franchise |
E52892
|
entity |
| Predicate | gameplayElement |
P15207
|
FINISHED |
| Object | first-person perspective |
—
|
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: first-person perspective | Statement: [Dishonored franchise, gameplayElement, first-person perspective]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gameplayElement Context triple: [Dishonored franchise, gameplayElement, first-person perspective]
-
A.
playInGameIntroduced
Indicates that an entity participates as a playable element within the specific game in which it was first introduced.
-
B.
eraPlayed
Indicates the historical or stylistic time period during which something (typically a work or performance) was played or took place.
-
C.
gameEngine
Indicates that one entity serves as the game engine or core runtime system used to develop, run, or power another entity (such as a game or interactive application).
-
D.
gameContext
chosen
Indicates the situational framework or environment in which a game’s actions, rules, and interactions take place.
-
E.
cityGame6
Indicates a relationship where an entity is associated with a specific city-based game, event, or competition labeled as variant 6.
- 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_69ab4959bcc0819083246f9fb10439e3 |
completed | March 6, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69abcc74a5108190a3a9631b0cc1a127 |
completed | March 7, 2026, 6:57 a.m. |
| PD | Predicate disambiguation | batch_69abc5aa1b60819081b87f7985c6cff3 |
completed | March 7, 2026, 6:28 a.m. |
Created at: March 6, 2026, 9:43 p.m.