Triple
T6533643
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anglers’ Rest |
E152291
|
entity |
| Predicate | typicalStoryType |
P11858
|
FINISHED |
| Object | tall tales |
—
|
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: tall tales | Statement: [Anglers’ Rest, typicalStoryType, tall tales]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalStoryType Context triple: [Anglers’ Rest, typicalStoryType, tall tales]
-
A.
narrativeType
chosen
Indicates the specific kind or category of narrative (e.g., genre, structural form, or storytelling mode) associated with an entity.
-
B.
storyBy
Indicates that one entity is the creator or author of the story associated with another entity.
-
C.
storyline
Indicates that one entity serves as the narrative plot or sequence of events associated with another entity.
-
D.
storyWorld
Indicates the fictional universe or narrative setting within which a story, event, or character exists or takes place.
-
E.
narrativePassage
Indicates that a segment of text functions as a narrative passage, conveying events, actions, or storytelling rather than exposition, dialogue, or other discourse types.
- 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.