Triple
T30687450
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Paley family |
E781224
|
entity |
| Predicate | hasNotableSpouseConnection |
P112532
|
FINISHED |
| Object | Babe Paley |
—
|
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: Babe Paley | Statement: [Paley family, hasNotableSpouseConnection, Babe Paley]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableSpouseConnection Context triple: [Paley family, hasNotableSpouseConnection, Babe Paley]
-
A.
hasNotableMarriage
Indicates a marital relationship involving the subject that is considered significant or noteworthy in some context.
-
B.
hasMemberSpouseConnection
Indicates a relationship where one entity is a spouse of a member associated with the other entity.
-
C.
hasNotablePersonConnection
Indicates that there exists a significant or noteworthy personal, professional, or historical relationship between the subject and the referenced person.
-
D.
hasNotableFamilyMembers
chosen
Indicates that an entity is related to one or more family members who are considered notable or significant in some context.
-
E.
hasPublicFigureSpouse
Indicates that a person’s spouse is a public figure, such as a celebrity, politician, or other widely recognized individual.
- 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_69f224a92f54819095499b4d32bd5134 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_6a004d0b46148190bcec4ea67acfe170 |
completed | May 10, 2026, 9:16 a.m. |
| PD | Predicate disambiguation | batch_6a004c92283081909f229c1720af155a |
completed | May 10, 2026, 9:14 a.m. |
Created at: April 29, 2026, 8:33 p.m.