Triple
T13773730
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kinderhook Reformed Dutch Church Cemetery |
E330945
|
entity |
| Predicate | dateOfFirstBurial |
P25906
|
FINISHED |
| Object | 18th century |
—
|
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: 18th century | Statement: [Kinderhook Reformed Dutch Church Cemetery, dateOfFirstBurial, 18th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dateOfFirstBurial Context triple: [Kinderhook Reformed Dutch Church Cemetery, dateOfFirstBurial, 18th century]
-
A.
dateOfBurial
Indicates the specific date on which an entity was buried.
-
B.
eraOfMostBurials
Indicates the historical time period during which the greatest number of burials occurred for a given site or context.
-
C.
firstBurial
Indicates that an entity is the earliest or initial burial associated with a person, place, or burial context.
-
D.
usedAsBurialGroundUntil
Indicates that a place functioned as a burial ground up to a specified end time or date.
-
E.
mainBurialsPeriodStart
chosen
Indicates the time period or date when the primary or main phase of burials at a site or within a context began.
- 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_69d81c583b0081909e408a17db517a21 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de023774b48190b19e43e87b94ba77 |
completed | April 14, 2026, 9 a.m. |
| PD | Predicate disambiguation | batch_69dbbe97846c819093b00ea117b64e0d |
completed | April 12, 2026, 3:47 p.m. |
Created at: April 9, 2026, 10:10 p.m.