Triple
T33421717
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Criterion Games |
E855862
|
entity |
| Predicate | notableEngineWork |
P20732
|
FINISHED |
| Object | RenderWare middleware |
E932245
|
NE 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: RenderWare middleware | Statement: [Criterion Games, notableEngineWork, RenderWare middleware]
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 (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_69f3496fdf0081908c1aa30870ce518b |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a037c8ae0248190b7e2ce4bf852c22d |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a357705178881908d6dbc113d86be79 |
completed | June 19, 2026, 5:06 p.m. |
| PD | Predicate disambiguation | batch_6a0379f505c88190ac0879ab422c3054 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:36 a.m.