Triple
T37927918
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Angelica Pickles |
E946140
|
entity |
| Predicate | auntOrUncleIs |
P3525
|
FINISHED |
| Object | Stu Pickles |
—
|
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: Stu Pickles | Statement: [Angelica Pickles, auntOrUncleIs, Stu Pickles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: auntOrUncleIs Context triple: [Angelica Pickles, auntOrUncleIs, Stu Pickles]
-
A.
uncleOrAuntOf
Indicates that one person is the uncle or aunt of another person, typically as the sibling (or sibling-in-law) of the other person’s parent.
-
B.
maternalAuntOrUncle
Indicates that one person is the sibling of another person's mother, regardless of the sibling's gender.
-
C.
auntOf
chosen
Indicates that one person is the aunt of another, typically as the sibling (or sibling-in-law) of a parent or sometimes an older female relative in an extended family role.
-
D.
hasAunt
Indicates that one entity is the aunt of another, typically meaning a sister (or sister-in-law) of a parent of that entity.
-
E.
isAuntWithin
Indicates that one person is the aunt of another within a specified familial or contextual boundary (such as a particular family, household, or lineage).
- 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_69f76ef3b7248190892fb9706423be7c |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fbc7b78f9481909f4f8fc2e3fdcde1 |
completed | May 6, 2026, 10:59 p.m. |
| PD | Predicate disambiguation | batch_69fbbd18c9908190928d274f8731dfa8 |
completed | May 6, 2026, 10:13 p.m. |
Created at: May 3, 2026, 4:20 p.m.