Triple
T31439574
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rogueport Item Shop |
E802029
|
entity |
| Predicate | hasInGameTimeAvailability |
P191763
|
FINISHED |
| Object | always open |
—
|
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: always open | Statement: [Rogueport Item Shop, hasInGameTimeAvailability, always open]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasInGameTimeAvailability Context triple: [Rogueport Item Shop, hasInGameTimeAvailability, always open]
-
A.
hasInGameActivities
Indicates that an entity includes or offers specific activities or actions that can be performed within a game context.
-
B.
playableInGame
Indicates that something can be used or controlled as an active element within a particular game.
-
C.
hasInGameService
Indicates that one entity provides or is associated with a service that is available or usable within a game environment.
-
D.
isFreeToPlay
Indicates that access to the game or activity does not require payment to participate.
-
E.
inGameTimePeriod
chosen
Indicates that an event, state, or action occurs within a specified time period in the context 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_69f348c5a6bc819092a557e95438976f |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69ff3e1762d8819089a60e402e682817 |
completed | May 9, 2026, 2 p.m. |
| PD | Predicate disambiguation | batch_69ff3d8c6f308190a0646b1432752eb8 |
completed | May 9, 2026, 1:58 p.m. |
Created at: April 30, 2026, 9:04 p.m.