Triple
T2483328
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arkane Studios |
E55868
|
entity |
| Predicate | gameDesignFocus |
P532
|
FINISHED |
| Object | first-person perspective |
—
|
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: first-person perspective | Statement: [Arkane Studios, gameDesignFocus, first-person perspective]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gameDesignFocus Context triple: [Arkane Studios, gameDesignFocus, first-person perspective]
-
A.
homeGamesFocus
Indicates a focus or emphasis on games played at a team's home venue rather than away or neutral-site games.
-
B.
designPhilosophy
chosen
Indicates the guiding principles, values, or conceptual approach that shape how something is designed or created.
-
C.
designLead
Indicates that one entity serves as the primary designer or person in charge of leading the design work for another entity or project.
-
D.
designProcess
Indicates the sequence of actions, decisions, and iterations involved in creating, developing, or refining a design.
-
E.
games
Indicates that one entity participates in, is associated with, or is characterized by playing or engaging in games with 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_69ab49e670a88190b928e08302381710 |
completed | March 6, 2026, 9:40 p.m. |
| NER | Named-entity recognition | batch_69abd20b6d008190acec0eb172e218c9 |
completed | March 7, 2026, 7:21 a.m. |
| PD | Predicate disambiguation | batch_69abd0b7cf088190bcff4dac6150044c |
completed | March 7, 2026, 7:16 a.m. |
Created at: March 6, 2026, 9:45 p.m.