Triple
T29194304
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Harolyn Suzanne Nicholas |
E740079
|
entity |
| Predicate | fatherNotableAs |
P166765
|
FINISHED |
| Object | member of the Nicholas Brothers dance duo |
—
|
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: member of the Nicholas Brothers dance duo | Statement: [Harolyn Suzanne Nicholas, fatherNotableAs, member of the Nicholas Brothers dance duo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fatherNotableAs Context triple: [Harolyn Suzanne Nicholas, fatherNotableAs, member of the Nicholas Brothers dance duo]
-
A.
fatherNotableFor
Indicates that a person's father is recognized or distinguished for a particular achievement, role, or characteristic.
-
B.
fatherNotability
Indicates that the subject’s father is notable or has a recognized level of prominence or significance.
-
C.
fatherAlsoKnownAs
Indicates that a person’s father is known or referred to by an alternative name or alias.
-
D.
notableHolderFather
Indicates that the notable holder of a title, position, or distinction is the father of the referenced person or entity.
-
E.
familyNotableMember
Indicates that a particular individual is a distinguished or noteworthy member of a given family.
- 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_69f07cb8033c8190b8807e219a14333d |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69f663c0a698819090eeeb219822e78a |
completed | May 2, 2026, 8:51 p.m. |
| PD | Predicate disambiguation | batch_69f660f2e3708190ab658652bcfc04d0 |
completed | May 2, 2026, 8:39 p.m. |
| PDg | Predicate description generation | batch_69f661e9cb308190a56e25dc17df248e |
completed | May 2, 2026, 8:43 p.m. |
Created at: April 28, 2026, 12:03 p.m.