Triple
T37256626
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anna Hauptmann |
E924145
|
entity |
| Predicate | residenceAfterHusbandArrest |
P188509
|
FINISHED |
| Object | New Jersey |
—
|
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: New Jersey | Statement: [Anna Hauptmann, residenceAfterHusbandArrest, New Jersey]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: residenceAfterHusbandArrest Context triple: [Anna Hauptmann, residenceAfterHusbandArrest, New Jersey]
-
A.
residenceAfterHusbandDeath
Indicates the place where a person resides following the death of their husband.
-
B.
residenceAfterRelease
Indicates the place where an individual lives or is located following their release from a prior confinement, custody, or institutional stay.
-
C.
residenceAfterSurrender
Indicates that an entity’s place of residence is recorded for the period following a surrender event (such as capitulation, handover, or formal yielding).
-
D.
residenceAfterDeposition
Indicates that an entity’s place of residence after a specified deposition event or process is at the related location.
-
E.
afterMarriageResidence
Indicates the place or arrangement where individuals live following their marriage.
- F. None of above. chosen
Provenance (4 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_69f76eabd6c481909d414a80a1345c98 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fba78aca4c8190b8f1831e8cc04e06 |
completed | May 6, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69fba34a65a4819088bac6c17542d71c |
completed | May 6, 2026, 8:23 p.m. |
| PDg | Predicate description generation | batch_69fba789c1188190973a919bfe2871f3 |
completed | May 6, 2026, 8:41 p.m. |
Created at: May 3, 2026, 4:15 p.m.