Triple
T11250082
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Initiative |
E266301
|
entity |
| Predicate | gameTypeSpecialization |
P8300
|
FINISHED |
| Object | single-player narrative 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 narrative experiences | Statement: [The Initiative, gameTypeSpecialization, single-player narrative experiences]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gameTypeSpecialization Context triple: [The Initiative, gameTypeSpecialization, single-player narrative experiences]
-
A.
ballGameType
Indicates the specific kind or category of ball game associated with an event or activity.
-
B.
primaryGameType
Indicates the main category or type of game with which an entity is primarily associated.
-
C.
hasGameType
chosen
Indicates that an entity (such as a game or match) is associated with a specific category or type of game.
-
D.
notableGameType
Indicates that a game is of a particular type or category for which the subject is especially well known or notable.
-
E.
includesGameType
Indicates that one entity contains or supports a particular type or category of game.
- 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_69d6aac7953c8190b82caf9d7640fdf9 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e93212448190b46b3799b0bdfa0f |
completed | April 9, 2026, 6 p.m. |
| PD | Predicate disambiguation | batch_69d78793c00481908a3f764b610b77a4 |
completed | April 9, 2026, 11:03 a.m. |
Created at: April 8, 2026, 9:31 p.m.