Triple
T33748837
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bates family mansion |
E864776
|
entity |
| Predicate | functionInStories |
P7328
|
FINISHED |
| Object | ancestral residence |
—
|
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: ancestral residence | Statement: [Bates family mansion, functionInStories, ancestral residence]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: functionInStories Context triple: [Bates family mansion, functionInStories, ancestral residence]
-
A.
storyFunction
chosen
Indicates that one entity serves a particular narrative role or function within the story structure of another entity.
-
B.
storyBy
Indicates that one entity is the creator or author of the story associated with another entity.
-
C.
worksOnStoryAbout
Indicates that one entity is actively engaged in creating, developing, or contributing to a story whose subject or focus is another entity.
-
D.
tellsStoriesIn
Indicates that one entity narrates or recounts stories within or to the context of another entity (such as a place, group, or medium).
-
E.
coreNarrative
Indicates the primary storyline or central sequence of events that forms the main thread of a narrative.
- 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_69f3498c35f881909df279ae4270f831 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f73223675481908c1bc3208c0f5284 |
completed | May 3, 2026, 11:31 a.m. |
| PD | Predicate disambiguation | batch_69f7317690108190b3aae2cd2e1d069e |
completed | May 3, 2026, 11:28 a.m. |
Created at: May 1, 2026, 1:45 a.m.