Triple
T29148689
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Summer ’03 |
E738841
|
entity |
| Predicate | hasGrandmotherCharacter |
P159187
|
FINISHED |
| Object | June Squibb’s character |
—
|
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: June Squibb’s character | Statement: [Summer ’03, hasGrandmotherCharacter, June Squibb’s character]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGrandmotherCharacter Context triple: [Summer ’03, hasGrandmotherCharacter, June Squibb’s character]
-
A.
hasMaternalGrandmother
Indicates that an entity has a specific individual who is its mother’s mother.
-
B.
isGranddaughterOf
Indicates that one person is the female child of another person's child.
-
C.
grandmother
Indicates that one entity is the female parent of another entity's parent.
-
D.
grandmotherFigure
chosen
Indicates a relationship where one entity serves in a grandmother-like, nurturing or elder female caregiver role toward another, regardless of biological or legal kinship.
-
E.
possibleGrandfatherOf
Indicates that one individual may be the grandfather of another, typically as the father of one of the other person’s parents, but with some uncertainty or lack of confirmation.
- 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_69f07cb46f148190874eb8576a447567 |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69f69383222c81909d8baa04129d5c81 |
completed | May 3, 2026, 12:14 a.m. |
| PD | Predicate disambiguation | batch_69f690eb1e948190aab41a89969519a5 |
completed | May 3, 2026, 12:03 a.m. |
Created at: April 28, 2026, 11:41 a.m.