Triple
T36963616
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Addermire Institute |
E914369
|
entity |
| Predicate | gameSeriesDeveloper |
P98722
|
FINISHED |
| Object | Arkane Studios |
—
|
NE NERFINISHED |
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: Arkane Studios | Statement: [Addermire Institute, gameSeriesDeveloper, Arkane Studios]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gameSeriesDeveloper Context triple: [Addermire Institute, gameSeriesDeveloper, Arkane Studios]
-
A.
gameDeveloperOfSeries
chosen
Indicates that a person or company is the developer responsible for creating or producing one or more games within a particular game series.
-
B.
gameDeveloper
Indicates that one entity creates, designs, or develops the other entity, which is a game.
-
C.
developerOfContainingGame
Indicates that an entity is the developer responsible for creating the game that contains the referenced element or component.
-
D.
gameDeveloperOwner
Indicates that one entity is the owner or primary controlling developer of a particular game.
-
E.
gameDeveloperOfAppearance
Indicates that an entity is the developer responsible for creating or producing a particular appearance or version of a 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_69f76e8c498c8190b2842db80aea8b3b |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fa0a7b00948190a257273d9968c5d7 |
completed | May 5, 2026, 3:19 p.m. |
| PD | Predicate disambiguation | batch_69f9fec9c9488190ae2a349651a02782 |
completed | May 5, 2026, 2:29 p.m. |
Created at: May 3, 2026, 4:14 p.m.