Triple
T36962998
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Hound Pits Pub |
E914353
|
entity |
| Predicate | hasInGameTimePeriod |
P56370
|
FINISHED |
| Object | plague-ridden era of Dunwall |
—
|
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: plague-ridden era of Dunwall | Statement: [The Hound Pits Pub, hasInGameTimePeriod, plague-ridden era of Dunwall]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasInGameTimePeriod Context triple: [The Hound Pits Pub, hasInGameTimePeriod, plague-ridden era of Dunwall]
-
A.
inGameTimePeriod
Indicates that an event, state, or action occurs within a specified time period in the context of a game.
-
B.
hasPhaseOfPlay
Indicates a relationship where a broader game or activity includes or is associated with a specific phase or segment of play.
-
C.
isSetInTimePeriod
chosen
Indicates that an event, story, or situation takes place within a specified time period.
-
D.
hasInGameActivities
Indicates that an entity includes or offers specific activities or actions that can be performed within a game context.
-
E.
playedInPeriod
Indicates that an entity participated or was active during a specified time period.
- 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_6a00cda99c908190980e0bf54cb2e2a4 |
completed | May 10, 2026, 6:25 p.m. |
| PD | Predicate disambiguation | batch_6a00cd1635b08190a791ecfcf87a1d54 |
completed | May 10, 2026, 6:23 p.m. |
Created at: May 3, 2026, 4:14 p.m.