Triple
T17509400
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dragon Age: Inquisition (score) |
E426409
|
entity |
| Predicate | supportsElementOfGame |
P52035
|
FINISHED |
| Object | world-building |
—
|
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: world-building | Statement: [Dragon Age: Inquisition (score), supportsElementOfGame, world-building]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsElementOfGame Context triple: [Dragon Age: Inquisition (score), supportsElementOfGame, world-building]
-
A.
supportsGames
Indicates that an entity is capable of running, handling, or being compatible with one or more games.
-
B.
gameElement
chosen
Indicates that one entity functions as a component, feature, or part within the structure or mechanics of a game.
-
C.
playableInGame
Indicates that something can be used or controlled as an active element within a particular game.
-
D.
supportsGameEngine
Indicates that one entity provides compatibility, functionality, or resources necessary for the operation or integration of a particular game engine.
-
E.
requiresBaseGame
Indicates that one item or content can only be used or accessed if a specified base game is already owned or installed.
- 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_69d889dd9164819087b1dc3c9240c870 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e4525a43208190b8728214767428c0 |
completed | April 19, 2026, 3:56 a.m. |
| PD | Predicate disambiguation | batch_69e3b4f5fbcc8190a6ea9639bf5650da |
completed | April 18, 2026, 4:44 p.m. |
Created at: April 10, 2026, 5:48 a.m.