Triple
T38604691
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LTI Gray Matter |
E934309
|
entity |
| Predicate | gameEngineDomain |
P166659
|
FINISHED |
| Object | 3D video games |
—
|
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: 3D video games | Statement: [LTI Gray Matter, gameEngineDomain, 3D video games]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gameEngineDomain Context triple: [LTI Gray Matter, gameEngineDomain, 3D video games]
-
A.
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).
-
B.
gameEngineType
chosen
Indicates the type or category of game engine associated with or used by an entity.
-
C.
gameEngineUsage
Indicates that one entity (such as a project or product) uses or is built upon a particular game engine.
-
D.
gameEngineWork
Indicates that an entity works on, contributes to, or is employed in the development or maintenance of a game engine.
-
E.
gameEngineOfWorkAppearedIn
Indicates that a particular game engine was used in the development or production of a specific work (such as a game or interactive media title).
- 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_69f76ecc17688190b389b693a5927501 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcdfbc71c481908ba7f87907b17782 |
completed | May 7, 2026, 6:53 p.m. |
| PD | Predicate disambiguation | batch_69fcdbe580b8819087f143596b2c79c0 |
completed | May 7, 2026, 6:37 p.m. |
Created at: May 3, 2026, 4:32 p.m.