Triple
T37782527
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bay 12 Games |
E941867
|
entity |
| Predicate | gameEngineApproach |
P159886
|
FINISHED |
| Object | custom in-house 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: custom in-house engine | Statement: [Bay 12 Games, gameEngineApproach, custom in-house engine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gameEngineApproach Context triple: [Bay 12 Games, gameEngineApproach, custom in-house engine]
-
A.
gameEngineDeveloper
Indicates that an entity is a developer responsible for creating or maintaining a game engine used to build video games.
-
B.
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).
-
C.
gameEngineUsage
chosen
Indicates that one entity (such as a project or product) uses or is built upon a particular game engine.
-
D.
gameEngineStyle
Indicates the stylistic or design approach characteristic of a particular game engine used in creating or presenting something.
-
E.
gameEngineType
Indicates the type or category of game engine associated with or used by an entity.
- 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_69f76ee5cb0c81909a363d1c929156c0 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fbb9e8108c8190ae1c7940b1677e95 |
completed | May 6, 2026, 10 p.m. |
| PD | Predicate disambiguation | batch_69fbb141605c8190b9c27d70352522db |
completed | May 6, 2026, 9:23 p.m. |
Created at: May 3, 2026, 4:19 p.m.