Triple
T35625858
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mr. Peanutbutter |
E1029448
|
entity |
| Predicate | notableShowWithinFiction |
P128697
|
FINISHED |
| Object | Mr. Peanutbutter’s House |
E2143837
|
NE 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: Mr. Peanutbutter’s House | Statement: [Mr. Peanutbutter, notableShowWithinFiction, Mr. Peanutbutter’s House]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableShowWithinFiction Context triple: [Mr. Peanutbutter, notableShowWithinFiction, Mr. Peanutbutter’s House]
-
A.
showWithinFiction
Indicates that one entity is depicted, referenced, or occurs as part of the fictional world or narrative context of another entity.
-
B.
notableFictionalFeature
Indicates that an entity is distinguished by a specific fictional characteristic, trait, or element it is known for.
-
C.
eraWithinFiction
Indicates that a time period or era exists inside the narrative world or timeline of a fictional work.
-
D.
notableShowWithinShow
chosen
Indicates that one show prominently features or contains another show within its narrative or structure.
-
E.
locationWithinFiction
Indicates that one fictional location is situated inside or contained within another fictional location.
- F. None of above.
Provenance (4 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_69f76e07bb0c8190968ea2d836fc42c9 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a037c8d06cc8190ab6a5e18d9d2571e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a38684ad5a081909b5550c809297a1a |
completed | June 21, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_6a037a04d8348190a4819666eab42c9b |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:05 p.m.