Triple
T29635189
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | First Reformed Church Cemetery, Hackensack |
E755691
|
entity |
| Predicate | hasGravemarkersFrom |
P87860
|
FINISHED |
| Object | Revolutionary War era |
—
|
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: Revolutionary War era | Statement: [First Reformed Church Cemetery, Hackensack, hasGravemarkersFrom, Revolutionary War era]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGravemarkersFrom Context triple: [First Reformed Church Cemetery, Hackensack, hasGravemarkersFrom, Revolutionary War era]
-
A.
hasGraveMarkersMaterial
Indicates that the material composition of grave markers is a specified substance or type.
-
B.
hasMarker
Indicates that one entity possesses, is associated with, or is identified by a specific marker.
-
C.
hasMarkerOrMonument
Indicates that something possesses or is associated with a physical marker or monument commemorating it.
-
D.
hasGraveMarkersFromPeriod
chosen
Indicates that an entity possesses grave markers that date from, or are associated with, a specified historical period.
-
E.
hasGravesFrom
Indicates that a location or site contains graves originating from or associated with a specified source place or group.
- 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_69f0ef88fbe081908f0ad90c1c413f1c |
completed | April 28, 2026, 5:34 p.m. |
| NER | Named-entity recognition | batch_69f6b2a65c7c8190ac40f1466ceadefc |
completed | May 3, 2026, 2:27 a.m. |
| PD | Predicate disambiguation | batch_69f6b14d7d508190bc7d4c89dfba4a32 |
completed | May 3, 2026, 2:22 a.m. |
Created at: April 28, 2026, 6:43 p.m.