Triple
T31439531
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rogueport Inn |
E802028
|
entity |
| Predicate | saveMechanicContext |
P23573
|
FINISHED |
| Object | save block interaction |
—
|
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: save block interaction | Statement: [Rogueport Inn, saveMechanicContext, save block interaction]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: saveMechanicContext Context triple: [Rogueport Inn, saveMechanicContext, save block interaction]
-
A.
restoringMechanism
Indicates a mechanism or process that returns something to its original, proper, or functional state after change, damage, or deviation.
-
B.
associatedWithMechanic
chosen
Indicates a relationship where an entity is connected or linked to a mechanic, such as a process, rule, or functional mechanism involved in its operation or behavior.
-
C.
recaptureContext
Indicates that a previously established context or situation is being regained or restored after it was lost, interrupted, or diminished.
-
D.
stateMutationMechanism
Indicates the process or method by which a system’s state is changed from one condition to another.
-
E.
restorationContext
Indicates the circumstances or setting in which something is being restored, including relevant conditions, constraints, and influencing factors surrounding the restoration process.
- 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_69f6a5f71b2c8190aade8a83f465be0c |
completed | May 3, 2026, 1:33 a.m. |
| PD | Predicate disambiguation | batch_69f69fe66df08190958558d63ee623d9 |
completed | May 3, 2026, 1:07 a.m. |
Created at: April 30, 2026, 9:04 p.m.