Triple
T33097714
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | St. Paul Episcopal Church Cemetery |
E846956
|
entity |
| Predicate | hasGravemarkersFromCentury |
P87860
|
FINISHED |
| Object | 19th 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: 19th century | Statement: [St. Paul Episcopal Church Cemetery, hasGravemarkersFromCentury, 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGravemarkersFromCentury Context triple: [St. Paul Episcopal Church Cemetery, hasGravemarkersFromCentury, 19th century]
-
A.
hasLaterAdditionsFromCentury
Indicates that additional elements or modifications were made to something in a later century than its original creation or primary period.
-
B.
hasGraveMarkersFromPeriod
chosen
Indicates that an entity possesses grave markers that date from, or are associated with, a specified historical period.
-
C.
attestedUntilCentury
Indicates the latest century up to which the existence or use of something is historically documented or evidenced.
-
D.
coveredSinceCentury
Indicates that one entity has been covered, coated, or kept under coverage continuously starting from a specified century.
-
E.
ownedInCentury
Indicates that one entity owned another during a specified century.
- 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_69f3495590dc8190aa04f3dec74ce976 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f7431c0eec81909ead443e07d75e18 |
completed | May 3, 2026, 12:44 p.m. |
| PD | Predicate disambiguation | batch_69f74143cf708190a12d487884298437 |
completed | May 3, 2026, 12:36 p.m. |
Created at: May 1, 2026, 1:26 a.m.