Triple
T31230085
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | June Cleaver in Still the Beaver |
E796255
|
entity |
| Predicate | reprisesRoleFrom |
P46748
|
FINISHED |
| Object | Leave It to Beaver |
—
|
NE NERFINISHED |
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: Leave It to Beaver | Statement: [June Cleaver in Still the Beaver, reprisesRoleFrom, Leave It to Beaver]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reprisesRoleFrom Context triple: [June Cleaver in Still the Beaver, reprisesRoleFrom, Leave It to Beaver]
-
A.
repetitionRole
Indicates that one entity serves a specific function or role within a repeated or recurring occurrence of another entity or event.
-
B.
reprisePerformersInStory
chosen
Indicates that certain performers reappear in the same roles or capacities within a subsequent part or version of the story.
-
C.
hasReprise
Indicates that an action, theme, or element is repeated or returns after its initial occurrence.
-
D.
actsInSteadOf
Indicates that one entity performs an action or fulfills a role as a substitute or proxy for another entity.
-
E.
musicalRole
Indicates the specific function or part an entity performs within a musical context, such as in a performance, composition, or ensemble.
- 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_69f224da98f88190ab32f690cce5d303 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69c6d50c08190b7011e9904e55922 |
completed | May 3, 2026, 12:53 a.m. |
| PD | Predicate disambiguation | batch_69f696673214819094350e1d2648ef34 |
completed | May 3, 2026, 12:27 a.m. |
Created at: April 29, 2026, 9:10 p.m.