Triple
T36133663
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Richard Nixon (second cousin) |
E1045096
|
entity |
| Predicate | sharesFamilyConnectionWith |
P151321
|
FINISHED |
| Object | Richard Nixon |
—
|
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: Richard Nixon | Statement: [Richard Nixon (second cousin), sharesFamilyConnectionWith, Richard Nixon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sharesFamilyConnectionWith Context triple: [Richard Nixon (second cousin), sharesFamilyConnectionWith, Richard Nixon]
-
A.
sharesFamilyWith
chosen
Indicates that two entities belong to the same family or share a familial relationship.
-
B.
sharesFamilyLineageWith
Indicates that two entities descend from the same family line or share common ancestors.
-
C.
familyConnectionTo
Indicates a familial relationship or bond that exists between two entities, such as by blood, marriage, or adoption.
-
D.
sharesChildrenWith
Indicates that two entities are co-parents, having one or more children in common.
-
E.
sharesParentsWith
Indicates that two entities have the same parents, making them siblings or otherwise sharing identical parentage.
- 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_69f76e36a4508190b5bfc8f594272a4c |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a0087de41c48190b2743a26b6d65409 |
completed | May 10, 2026, 1:27 p.m. |
| PD | Predicate disambiguation | batch_6a00870a8bc48190be1385579b8cc1dd |
completed | May 10, 2026, 1:24 p.m. |
Created at: May 3, 2026, 4:08 p.m.