Triple
T2557340
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Telltale Games |
E56755
|
entity |
| Predicate | gameplayEmphasis |
P3775
|
FINISHED |
| Object | player choice |
—
|
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: player choice | Statement: [Telltale Games, gameplayEmphasis, player choice]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gameplayEmphasis Context triple: [Telltale Games, gameplayEmphasis, player choice]
-
A.
styleOfPlay
chosen
Indicates the characteristic manner or approach in which an entity performs or behaves, especially in a game, sport, or artistic context.
-
B.
featuresHighStakesGames
Indicates that something includes or offers games involving significant risk, tension, or major consequences for the participants.
-
C.
strategyEmphasis
Indicates an entity’s primary focus or priority within a broader strategy or plan.
-
D.
usedInPlayByPlayFor
Indicates that something (such as data, terminology, or a resource) is utilized within the context of a play-by-play account or commentary.
-
E.
homeGamesFocus
Indicates a focus or emphasis on games played at a team's home venue rather than away or neutral-site games.
- 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_69ab4a4bfec081908039988ec4c86e28 |
completed | March 6, 2026, 9:42 p.m. |
| NER | Named-entity recognition | batch_69abd35c6ee88190b6eaa1841d3e99a4 |
completed | March 7, 2026, 7:27 a.m. |
| PD | Predicate disambiguation | batch_69abd0caeb488190b0dd8e48d0f2777d |
completed | March 7, 2026, 7:16 a.m. |
Created at: March 6, 2026, 9:48 p.m.