Triple
T6533644
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anglers’ Rest |
E152291
|
entity |
| Predicate | typicalStoryTone |
P5869
|
FINISHED |
| Object | humorous |
—
|
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: humorous | Statement: [Anglers’ Rest, typicalStoryTone, humorous]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalStoryTone Context triple: [Anglers’ Rest, typicalStoryTone, humorous]
-
A.
narrativeType
Indicates the specific kind or category of narrative (e.g., genre, structural form, or storytelling mode) associated with an entity.
-
B.
narrativeStyle
chosen
Indicates how a narrative is told, such as the point of view, tone, and structural approach used to present a story or account.
-
C.
storyBy
Indicates that one entity is the creator or author of the story associated with another entity.
-
D.
typicalSpeaker
Indicates that the subject is a prototypical or characteristic speaker or source of utterances in the context of the object.
-
E.
typicalDialogueStyle
Indicates the characteristic manner or pattern in which an entity typically communicates or conducts dialogue.
- 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_69c688048ec8819093a47f7d332e12ec |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6adbf3a748190b0fb52122faaf6d3 |
completed | March 27, 2026, 4:18 p.m. |
| PD | Predicate disambiguation | batch_69c68abd9c7c819099e4fe8097cd1b28 |
completed | March 27, 2026, 1:48 p.m. |
Created at: March 27, 2026, 1:46 p.m.