Triple
T24754963
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anne Eisenhower |
E619256
|
entity |
| Predicate | hasNotableRelativeRole |
P123178
|
FINISHED |
| Object | granddaughter of 34th U.S. President |
—
|
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: granddaughter of 34th U.S. President | Statement: [Anne Eisenhower, hasNotableRelativeRole, granddaughter of 34th U.S. President]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableRelativeRole Context triple: [Anne Eisenhower, hasNotableRelativeRole, granddaughter of 34th U.S. President]
-
A.
hasRelativeRole
Indicates that one entity holds a familial or kinship-based role in relation to another entity.
-
B.
hasNotableRoleIn
Indicates that an entity holds a significant or noteworthy role or function within another entity, event, work, or context.
-
C.
hasNotableRelativeGroup
Indicates that an entity is associated with a group of relatives who are notable or significant in some recognized way.
-
D.
notableRelative
Indicates that an entity has a relative who is notable or well-known, specifying that familial relationship.
-
E.
notableRelativeType
chosen
Indicates the specific familial or relational role that a notable relative has in relation to the subject.
- 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_69e2fabb349881908a13a212a0221a63 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f55e519978819087a1676564a74630 |
completed | May 2, 2026, 2:15 a.m. |
| PD | Predicate disambiguation | batch_69f4a0edd10c81908a052ab864d57c54 |
completed | May 1, 2026, 12:47 p.m. |
Created at: April 18, 2026, 4:26 a.m.