Triple
T27018663
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eliza Burr |
E680603
|
entity |
| Predicate | startTimeOfSpouse_StephenJumel |
P67588
|
FINISHED |
| Object | 1804 |
—
|
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: 1804 | Statement: [Eliza Burr, startTimeOfSpouse_StephenJumel, 1804]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: startTimeOfSpouse_StephenJumel Context triple: [Eliza Burr, startTimeOfSpouse_StephenJumel, 1804]
-
A.
endTimeOfSpouse_StephenJumel
Indicates the time at which the marital relationship involving Stephen Jumel’s spouse comes to an end.
-
B.
spouseOfSince
chosen
Indicates that two individuals are spouses and specifies the date or time from which their marital relationship has been in effect.
-
C.
startTimeOfSpouseRelationshipWith John Jacob Astor IV
Indicates the point in time when John Jacob Astor IV’s spousal relationship with a partner began.
-
D.
metSpouseAt
Indicates that one person first encountered or became acquainted with their spouse at a particular place, event, or time.
-
E.
allegedSpouseOf
Indicates a relationship where one person is claimed or reported to be the spouse of another, but the marital status is not legally or definitively confirmed.
- 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_69eeeb5450988190bfc9a3c012ac463a |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69f7c777e924819081a6634f549fe552 |
completed | May 3, 2026, 10:08 p.m. |
| PD | Predicate disambiguation | batch_69f7c475c58c8190a883554231e88c88 |
completed | May 3, 2026, 9:56 p.m. |
Created at: April 27, 2026, 7:07 a.m.