Triple
T16709943
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aunt Polly's house |
E406079
|
entity |
| Predicate | hasPartInStory |
P38554
|
FINISHED |
| Object | kitchen |
—
|
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: kitchen | Statement: [Aunt Polly's house, hasPartInStory, kitchen]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPartInStory Context triple: [Aunt Polly's house, hasPartInStory, kitchen]
-
A.
hasPartInNarrative
chosen
Indicates that one entity plays a role or participates as a component within the storyline or structure of another narrative entity.
-
B.
hasSiblingInStory
Indicates that one character in a narrative has at least one sibling who also appears within the same story.
-
C.
hasAllyInStory
Indicates that one entity is portrayed as an ally or supportive partner of another entity within the context of a specific story or narrative.
-
D.
appearsInShortStoryBy
Indicates that one entity is a character, element, or subject that appears within a short story authored by another entity.
-
E.
hasAwardInStory
Indicates that an entity is depicted within a narrative or story as having received a particular award.
- 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_69d8838db21081909589220fd71440a4 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3865186b48190bb45a761f5cf1a83 |
completed | April 18, 2026, 1:25 p.m. |
| PD | Predicate disambiguation | batch_69e319c379f88190ac0adf812486f598 |
completed | April 18, 2026, 5:42 a.m. |
Created at: April 10, 2026, 5:20 a.m.