Triple
T29341671
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Infinity Engine |
E744051
|
entity |
| Predicate | inspiredGame |
P44629
|
FINISHED |
| Object | Pillars of Eternity |
—
|
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: Pillars of Eternity | Statement: [Infinity Engine, inspiredGame, Pillars of Eternity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inspiredGame Context triple: [Infinity Engine, inspiredGame, Pillars of Eternity]
-
A.
inspiredVideoGame
chosen
Indicates that one entity served as the creative basis or influence for the development or design of a video game.
-
B.
designedGame
Indicates that one entity is the creator or designer responsible for the conception and development of a particular game.
-
C.
inspiredPlayer
Indicates that one player has motivated, influenced, or sparked creativity or performance in another player.
-
D.
inspiredSpinOff
Indicates that one entity served as the creative or conceptual inspiration for another entity that was developed as a spin-off.
-
E.
originGame
Indicates the game from which an entity, such as a character, item, or concept, originally comes.
- 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_69f09126cfcc8190899b16fbf3c2bf7b |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69f6d6a6b04c8190bee4cf9c00665ef7 |
completed | May 3, 2026, 5:01 a.m. |
| PD | Predicate disambiguation | batch_69f6d26ceb08819091c71c001e954936 |
completed | May 3, 2026, 4:43 a.m. |
Created at: April 28, 2026, 1:34 p.m.