Triple
T3235431
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Trader Sam's Grog Grotto |
E67842
|
entity |
| Predicate | immersiveStorytelling |
P30765
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Trader Sam's Grog Grotto, immersiveStorytelling, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: immersiveStorytelling Context triple: [Trader Sam's Grog Grotto, immersiveStorytelling, yes]
-
A.
immersesVisitorsIn
chosen
Indicates that one entity deeply involves or surrounds visitors in an experience, environment, or atmosphere created by another entity.
-
B.
narrativeFrame
Indicates the overarching narrative context or perspective within which events, actions, or relationships are presented or interpreted.
-
C.
narrativeType
Indicates the specific kind or category of narrative (e.g., genre, structural form, or storytelling mode) associated with an entity.
-
D.
hasNarrativeDevice
Indicates that one entity employs, contains, or is characterized by a particular narrative device used in storytelling or discourse.
-
E.
narrative
Indicates that one entity tells, presents, or conveys a story or sequence of events about another entity or situation.
- 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_69ad858d27348190abb61c280b4c86a9 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69adaede0bdc8190a466f11bf2c50836 |
completed | March 8, 2026, 5:16 p.m. |
| PD | Predicate disambiguation | batch_69ada4159e0481908cbbdd750f5e08c7 |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:08 p.m.