Triple
T27756328
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cinematronics LLC |
E701341
|
entity |
| Predicate | gameEngineWork |
P163220
|
FINISHED |
| Object | pinball physics simulation |
—
|
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: pinball physics simulation | Statement: [Cinematronics LLC, gameEngineWork, pinball physics simulation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gameEngineWork Context triple: [Cinematronics LLC, gameEngineWork, pinball physics simulation]
-
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.
gameEngineUsage
Indicates that one entity (such as a project or product) uses or is built upon a particular game engine.
-
C.
gameEngineReuseIn
Indicates that one game reuses or is implemented using the game engine from another game or source.
-
D.
gameEngineModification
Indicates a relationship where an entity alters, extends, or customizes the functionality or behavior of a game engine.
-
E.
gameContext
Indicates the situational framework or environment in which a game’s actions, rules, and interactions take place.
- F. None of above. chosen
Provenance (4 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_69ef6a5193808190816eb7d0020b2d87 |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f63760b350819088f0eca0257ca125 |
completed | May 2, 2026, 5:41 p.m. |
| PD | Predicate disambiguation | batch_69f63188e7408190af8ce8b93d128c63 |
completed | May 2, 2026, 5:16 p.m. |
| PDg | Predicate description generation | batch_69f6352df6148190bc10772cd40bd7b3 |
completed | May 2, 2026, 5:32 p.m. |
Created at: April 27, 2026, 4:23 p.m.