Triple
T849879
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Elisabeth Pepys |
E18359
|
entity |
| Predicate | domesticRole |
P268
|
FINISHED |
| Object | wife in a 17th-century London household |
—
|
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: wife in a 17th-century London household | Statement: [Elisabeth Pepys, domesticRole, wife in a 17th-century London household]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: domesticRole Context triple: [Elisabeth Pepys, domesticRole, wife in a 17th-century London household]
-
A.
typicalRole
Indicates that one entity serves as the usual, characteristic, or commonly expected role or function of another entity.
-
B.
familyAspect
Indicates a relationship where one entity is characterized by a particular familial role, status, or aspect in relation to another entity.
-
C.
role
chosen
Indicates the function, position, or responsibility that one entity holds in relation to another within a given context.
-
D.
household
Indicates that two or more entities belong to or are part of the same household unit, typically sharing a residence and domestic life.
-
E.
family
Indicates a familial relationship or connection between entities, such as being related by blood, marriage, or adoption.
- 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_69a4938b04208190b82e1df6b572c548 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4ac215194819099e6bc1b5df58fb3 |
completed | March 1, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69a4aa807adc8190ad808a573cf8e923 |
completed | March 1, 2026, 9:07 p.m. |
Created at: March 1, 2026, 7:38 p.m.