Triple
T26267869
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dannielynn Birkhead |
E657037
|
entity |
| Predicate | paternityConfirmedBy |
P160184
|
FINISHED |
| Object | DNA test |
—
|
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: DNA test | Statement: [Dannielynn Birkhead, paternityConfirmedBy, DNA test]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: paternityConfirmedBy Context triple: [Dannielynn Birkhead, paternityConfirmedBy, DNA test]
-
A.
paternalStatus
Indicates the nature or condition of a paternal relationship that an entity has to another (e.g., being a father, presumed father, or having a specific paternal role or status).
-
B.
paternityConcealedFrom
Indicates that one party’s biological fatherhood of another is intentionally hidden or not disclosed from a specified person or group.
-
C.
hasPossibleFather
Indicates a relationship where a given individual may be the father of another, but this parentage is not confirmed.
-
D.
spouseParentage
Indicates that one entity is a parent of the other entity’s spouse.
-
E.
hasHolderFather
Indicates that an entity has a father who serves as the holder or custodian of that entity.
- 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_69ee5b4e21bc819082be98bc9ab09796 |
completed | April 26, 2026, 6:37 p.m. |
| NER | Named-entity recognition | batch_69f60e2ef4bc8190b1ca37c0daf80ea4 |
completed | May 2, 2026, 2:46 p.m. |
| PD | Predicate disambiguation | batch_69f5f7ff548c8190a23e98c5e66e0bc7 |
completed | May 2, 2026, 1:11 p.m. |
| PDg | Predicate description generation | batch_69f5ffc6268c8190b63f6360ebadab73 |
completed | May 2, 2026, 1:44 p.m. |
Created at: April 26, 2026, 9:12 p.m.