Triple
T17866240
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | White Witch of Rose Hall |
E446710
|
entity |
| Predicate | storyToldIn |
P35676
|
FINISHED |
| Object | guided tours of Rose Hall |
—
|
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: guided tours of Rose Hall | Statement: [White Witch of Rose Hall, storyToldIn, guided tours of Rose Hall]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: storyToldIn Context triple: [White Witch of Rose Hall, storyToldIn, guided tours of Rose Hall]
-
A.
storyBy
Indicates that one entity is the creator or author of the story associated with another entity.
-
B.
storyTime
Indicates that one entity is narrating or sharing a story with another entity, typically in a designated or scheduled period for storytelling.
-
C.
retellsStoryOf
Indicates that one entity recounts or narrates the story originally told or experienced by another entity.
-
D.
originStoryIncludes
Indicates that an entity’s origin story contains, involves, or features the referenced element as a component or part of that backstory.
-
E.
storyElement
chosen
Indicates that one entity functions as a narrative component or part within the structure of another entity’s story.
- 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_69d8b9f4c22c819093c2680434472894 |
completed | April 10, 2026, 8:51 a.m. |
| NER | Named-entity recognition | batch_69e49793a2588190bb341ac606d767fe |
completed | April 19, 2026, 8:51 a.m. |
| PD | Predicate disambiguation | batch_69e3d8e6d2e88190ad9ef9f8a99f13e6 |
completed | April 18, 2026, 7:17 p.m. |
Created at: April 10, 2026, 10:17 a.m.