Triple
T2292370
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anna de Witt |
E51532
|
entity |
| Predicate | familyRelationContext |
P8517
|
FINISHED |
| Object | daughter of an influential statesman |
—
|
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: daughter of an influential statesman | Statement: [Anna de Witt, familyRelationContext, daughter of an influential statesman]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: familyRelationContext Context triple: [Anna de Witt, familyRelationContext, daughter of an influential statesman]
-
A.
familyOf
Indicates a familial relationship exists between the entities, such as by blood, marriage, or adoption.
-
B.
familyAspect
chosen
Indicates a relationship where one entity is characterized by a particular familial role, status, or aspect in relation to another entity.
-
C.
relationshipType
Indicates the specific kind of relationship that exists between two or more entities.
-
D.
geneticRelation
Indicates that two entities are connected through a hereditary or familial genetic relationship.
-
E.
historicalRelationship
Indicates a relationship that existed between entities in the past, often tied to a specific historical period, context, or event.
- 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_69a88b09c644819090b503456d96bf70 |
completed | March 4, 2026, 7:42 p.m. |
| NER | Named-entity recognition | batch_69abcd0e42248190ada33b84d75caa64 |
completed | March 7, 2026, 7 a.m. |
| PD | Predicate disambiguation | batch_69abc589295c819092989820c2b4e9d8 |
completed | March 7, 2026, 6:28 a.m. |
Created at: March 4, 2026, 7:48 p.m.