Triple
T35222780
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Charles G. Gates |
E1017003
|
entity |
| Predicate | notableAliasOfFather |
P93919
|
FINISHED |
| Object | "Bet-a-Million" Gates |
E1004364
|
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: "Bet-a-Million" Gates | Statement: [Charles G. Gates, notableAliasOfFather, "Bet-a-Million" Gates]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableAliasOfFather Context triple: [Charles G. Gates, notableAliasOfFather, "Bet-a-Million" Gates]
-
A.
notableHolderFather
Indicates that the notable holder of a title, position, or distinction is the father of the referenced person or entity.
-
B.
fatherNotableAs
Indicates that someone is recognized or distinguished specifically in their role as a father.
-
C.
fatherAlsoKnownAs
chosen
Indicates that a person’s father is known or referred to by an alternative name or alias.
-
D.
fatherNotability
Indicates that the subject’s father is notable or has a recognized level of prominence or significance.
-
E.
fatherNotableFor
Indicates that a person's father is recognized or distinguished for a particular achievement, role, or characteristic.
- 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_69f76de072908190ab65038a8a7b6a79 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a037c8c34f88190ace26f555827f23e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3804156c308190b95cb35fbe967731 |
completed | June 21, 2026, 3:32 p.m. |
| PD | Predicate disambiguation | batch_6a037a016960819093ed4990fb4d9d36 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:02 p.m.