Triple
T25199359
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ArtPlay |
E631083
|
entity |
| Predicate | gameDevelopmentFocus |
P158021
|
FINISHED |
| Object | single-player experiences |
—
|
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: single-player experiences | Statement: [ArtPlay, gameDevelopmentFocus, single-player experiences]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gameDevelopmentFocus Context triple: [ArtPlay, gameDevelopmentFocus, single-player experiences]
-
A.
gameDevelopmentFocus
chosen
Indicates that an entity’s primary attention, effort, or specialization is directed toward the creation and production of games.
-
B.
hasDevelopmentFocus
Indicates that an entity is primarily concerned with or directed toward a particular area, goal, or aspect of development.
-
C.
developmentFocusedOn
Indicates that the primary effort or activity of development is directed toward a specific target, aspect, or objective.
-
D.
gameDevelopmentPlatform
Indicates a platform or environment used for creating, developing, and possibly deploying games.
-
E.
developmentCategory
Indicates the classification of an entity according to a particular stage, type, or area of development.
- 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_69e75a8b86c4819089eda22c843b739f |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f474b409808190b41f2edafc801130 |
completed | May 1, 2026, 9:39 a.m. |
| PD | Predicate disambiguation | batch_69f45cfb53f4819099bba48c5057e787 |
completed | May 1, 2026, 7:57 a.m. |
Created at: April 21, 2026, 12:51 p.m.