Triple
T35511448
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Iliac Bay region |
E1026293
|
entity |
| Predicate | gameplayFeatureIn |
P92849
|
FINISHED |
| Object | procedurally generated wilderness in Daggerfall |
—
|
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: procedurally generated wilderness in Daggerfall | Statement: [Iliac Bay region, gameplayFeatureIn, procedurally generated wilderness in Daggerfall]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gameplayFeatureIn Context triple: [Iliac Bay region, gameplayFeatureIn, procedurally generated wilderness in Daggerfall]
-
A.
gameFeatures
chosen
Indicates that a game includes or offers a particular element, characteristic, or functionality.
-
B.
featuresGame
Indicates that something (such as a platform, service, or collection) includes or presents a particular game as part of its offerings.
-
C.
notableGameFeature
Indicates that a particular game feature is especially significant, distinctive, or noteworthy in the context of the game.
-
D.
playableInGame
Indicates that something can be used or controlled as an active element within a particular game.
-
E.
playInGameIntroduced
Indicates that an entity participates as a playable element within the specific game in which it was first introduced.
- 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_69f76dfd61208190b93ec6dc439cab41 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f79ec355048190af30123ceb6efa2b |
completed | May 3, 2026, 7:15 p.m. |
| PD | Predicate disambiguation | batch_69f79e4bdbcc8190be7a0d2cf8a77b64 |
completed | May 3, 2026, 7:13 p.m. |
Created at: May 3, 2026, 4:04 p.m.