Triple
T31439537
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rogueport Inn |
E802028
|
entity |
| Predicate | supportsPlayerAction |
P82156
|
FINISHED |
| Object | rest |
—
|
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: rest | Statement: [Rogueport Inn, supportsPlayerAction, rest]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsPlayerAction Context triple: [Rogueport Inn, supportsPlayerAction, rest]
-
A.
supportsPlayer
Indicates that one entity provides assistance, resources, or backing to a player in achieving their goals or performing actions.
-
B.
supportsPlayers
Indicates that an entity provides compatibility or functionality for one or more players to participate or be used.
-
C.
allowsPlayerAction
chosen
Indicates that one entity permits or enables a player to perform a specific action within a system or context.
-
D.
supportsActionSpace
Indicates that one entity is capable of enabling, handling, or being compatible with a specified action space for operations or behaviors.
-
E.
supportsMusicPlayer
Indicates that one entity provides compatibility with or functionality for operating a music player associated with another entity.
- 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_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379e5174c8190a0bdde7e381b7624 |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 30, 2026, 9:04 p.m.