Triple
T35014923
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gumbald |
E1010027
|
entity |
| Predicate | formerRelativeOf |
P201994
|
FINISHED |
| Object | Princess Bubblegum |
—
|
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: Princess Bubblegum | Statement: [Gumbald, formerRelativeOf, Princess Bubblegum]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formerRelativeOf Context triple: [Gumbald, formerRelativeOf, Princess Bubblegum]
-
A.
appointedRelative
Indicates that one entity has formally assigned or designated another entity, who is a relative, to a specific role, position, or responsibility.
-
B.
relationshipToRelative
Indicates the specific familial connection or kinship role that one person has in relation to a particular relative.
-
C.
paternalRelativeOf
Indicates a family relationship where one person is a relative of another specifically through the father’s side of the family.
-
D.
forefatherOf
Indicates that one person is an ancestor, typically from an earlier generation, of another person.
-
E.
relationToAncestors
Indicates a familial relationship that connects an entity to one or more of its ancestors in a lineage or hierarchy.
- F. None of above. chosen
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_69f76dcc3ac8819096a3ed52f5fa2523 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a0041860fd081908623ef9fd40a9775 |
completed | May 10, 2026, 8:27 a.m. |
| PD | Predicate disambiguation | batch_6a00414b01488190a312adb3b25d69cf |
completed | May 10, 2026, 8:26 a.m. |
| PDg | Predicate description generation | batch_6a00418517008190b33399a08a003ee2 |
completed | May 10, 2026, 8:27 a.m. |
Created at: May 3, 2026, 4:01 p.m.