Triple
T33421717
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Criterion Games |
E855862
|
entity |
| Predicate | notableEngineWork |
—
|
GENERATED |
| Object | RenderWare middleware |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableEngineWork Context triple: [Criterion Games, notableEngineWork, RenderWare middleware]
-
A.
notableEngineType
Indicates that an entity is particularly recognized for using or being associated with a specific type of engine.
-
B.
notableWorkPerformed
chosen
Indicates that an entity has created, executed, or contributed significantly to a particular work that is recognized as notable or important.
-
C.
hasMajorWork
Indicates that an entity (typically a person, creator, or organization) is associated with a significant or principal work they produced or are best known for.
-
D.
crewNote
Indicates that a note or comment is recorded about a crew member or crew-related activity.
-
E.
notableWorker
Indicates that the subject is a worker who is distinguished or recognized for being particularly important, prominent, or exemplary in their work.
- F. None of above.
Provenance (1 batch)
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_69f3496fdf0081908c1aa30870ce518b |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:36 a.m.