Triple
T14717537
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amelia Watts |
E345719
|
entity |
| Predicate | notable family role |
P367
|
FINISHED |
| Object | mother of a British Prime Minister |
—
|
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: mother of a British Prime Minister | Statement: [Amelia Watts, notable family role, mother of a British Prime Minister]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notable family role Context triple: [Amelia Watts, notable family role, mother of a British Prime Minister]
-
A.
notableFamilyFor
Indicates that a family is particularly recognized or distinguished for a specific person, achievement, role, or characteristic.
-
B.
hasFamilyRole
Indicates that one entity holds a specific familial role or position in relation to another entity.
-
C.
notableFamilyIn
Indicates that a person is notably associated with or belongs to a particular family within a given place or context.
-
D.
notableRelative
chosen
Indicates that an entity has a relative who is notable or well-known, specifying that familial relationship.
-
E.
depictsNotableFamily
Indicates that something visually represents or portrays a family that is considered notable or significant.
- 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_69d822e5911c8190ba589f957dbd9ba7 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb98688f48190b2b19ce7aa06a6db |
completed | April 14, 2026, 10:02 p.m. |
| PD | Predicate disambiguation | batch_69de657e174481909da0437556334a04 |
completed | April 14, 2026, 4:04 p.m. |
Created at: April 10, 2026, 1:29 a.m.