Triple
T35229654
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stephen Symonds Foster |
E1017193
|
entity |
| Predicate | sharesBurialPlaceWith |
P199639
|
FINISHED |
| Object | Abby Kelley Foster |
—
|
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: Abby Kelley Foster | Statement: [Stephen Symonds Foster, sharesBurialPlaceWith, Abby Kelley Foster]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sharesBurialPlaceWith Context triple: [Stephen Symonds Foster, sharesBurialPlaceWith, Abby Kelley Foster]
-
A.
sharesGraveWith
chosen
Indicates that two or more individuals are buried in the same grave or burial plot.
-
B.
associatedCemetery
Indicates that there is a relationship linking an entity (such as a person, event, or organization) to a specific cemetery with which it is connected.
-
C.
burialPlace
Indicates the location where a person or entity is buried.
-
D.
burialPlaceOfManyMembers
Indicates a location that serves as the burial site for multiple members of a particular group, family, or organization.
-
E.
alsoBurials
Indicates that the subject location or record includes additional burial sites or burial events beyond the primary one referenced.
- 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_69f76de12e4c8190bc46b71a32858356 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a00532815c881908f10d9594458b3d7 |
completed | May 10, 2026, 9:43 a.m. |
| PD | Predicate disambiguation | batch_6a0052b9f030819081b8105bdcaf6d8f |
completed | May 10, 2026, 9:41 a.m. |
Created at: May 3, 2026, 4:02 p.m.