Triple
T2557349
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Telltale Games |
E56755
|
entity |
| Predicate | gameEngineUse |
P26587
|
FINISHED |
| Object | proprietary engine |
—
|
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: proprietary engine | Statement: [Telltale Games, gameEngineUse, proprietary engine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gameEngineUse Context triple: [Telltale Games, gameEngineUse, proprietary engine]
-
A.
gameEngine
chosen
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).
-
B.
gameContext
Indicates the situational framework or environment in which a game’s actions, rules, and interactions take place.
-
C.
gameDirector
Indicates that one entity serves as the director (creative or managerial lead) of a particular game associated with another entity.
-
D.
postGamesUse
Indicates that an entity uses or engages with something after games have concluded.
-
E.
gameState
Indicates the current status or condition of a game at a particular point in time, including relevant rules, progress, and contextual information.
- 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.