Triple
T31894665
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Keats family |
E814246
|
entity |
| Predicate | hasParentOfNotableMember |
P70430
|
FINISHED |
| Object | Thomas Keats Sr. |
—
|
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: Thomas Keats Sr. | Statement: [Keats family, hasParentOfNotableMember, Thomas Keats Sr.]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasParentOfNotableMember Context triple: [Keats family, hasParentOfNotableMember, Thomas Keats Sr.]
-
A.
hasNotableParent
chosen
Indicates that an entity has a parent who is distinguished, prominent, or otherwise notable.
-
B.
hasNotableMember
Indicates that a group, organization, or collection includes at least one member who is distinguished or noteworthy in some significant way.
-
C.
hasNotableFamilyInField
Indicates that an individual has family members who are recognized or distinguished within a particular professional or academic field.
-
D.
hasNotableDescendant
Indicates that an entity has at least one descendant who is recognized as notable or significant in some context.
-
E.
hasNotableFamilyMembers
Indicates that an entity is related to one or more family members who are considered notable or significant in some context.
- 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_69f348ef817481908440e2250319bcc8 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fed6da0390819096b88ef4714b144e |
completed | May 9, 2026, 6:40 a.m. |
| PD | Predicate disambiguation | batch_69fed53517d081909966f31707625f1a |
completed | May 9, 2026, 6:33 a.m. |
Created at: April 30, 2026, 11:58 p.m.