Triple
T28896127
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Guard Crush Games |
E732837
|
entity |
| Predicate | gameDevelopmentDiscipline |
P62830
|
FINISHED |
| Object | game programming |
—
|
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: game programming | Statement: [Guard Crush Games, gameDevelopmentDiscipline, game programming]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gameDevelopmentDiscipline Context triple: [Guard Crush Games, gameDevelopmentDiscipline, game programming]
-
A.
gameDevelopmentFocus
Indicates that an entity’s primary attention, effort, or specialization is directed toward the creation and production of games.
-
B.
gameDeveloper
Indicates that one entity creates, designs, or develops the other entity, which is a game.
-
C.
gameDevelopmentPlatform
Indicates a platform or environment used for creating, developing, and possibly deploying games.
-
D.
designDiscipline
chosen
Indicates a relationship where an entity is associated with, categorized under, or practices a particular field or branch of design.
-
E.
developmentPillar
Indicates that one entity serves as a fundamental pillar or core focus area supporting the development or growth of another 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_69f05b08c2008190ac426a035a2ed66d |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69f65b14512c8190a40e70319dcc54cd |
completed | May 2, 2026, 8:14 p.m. |
| PD | Predicate disambiguation | batch_69f659d02f1c8190831758ac52bb54e4 |
completed | May 2, 2026, 8:08 p.m. |
Created at: April 28, 2026, 7:59 a.m.