Triple
T8024633
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sylvan Water |
E186821
|
entity |
| Predicate | locatedWithinCemeterySection |
P40046
|
FINISHED |
| Object | northern area of Green-Wood Cemetery |
—
|
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: northern area of Green-Wood Cemetery | Statement: [Sylvan Water, locatedWithinCemeterySection, northern area of Green-Wood Cemetery]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedWithinCemeterySection Context triple: [Sylvan Water, locatedWithinCemeterySection, northern area of Green-Wood Cemetery]
-
A.
locatedInCemetery
Indicates that one entity is situated within the grounds or area of a cemetery.
-
B.
cemeterySection
chosen
Indicates that one entity is a specific section, area, or subdivision within a cemetery associated with the other entity.
-
C.
isCemeteryFor
Indicates that one entity serves as the burial ground designated for another entity, such as a community, group, or location.
-
D.
cemeteryArea
Indicates that an area or region is designated, used, or recognized as a cemetery.
-
E.
hasCemetery
Indicates that one entity possesses, contains, or includes a cemetery associated with it.
- 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_69ca82ad4e2c8190a693e3c9e30fe66f |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3e90c7348190abc1013a312e4f1a |
completed | March 31, 2026, 3:25 a.m. |
| PD | Predicate disambiguation | batch_69cb049253d08190bafcecfde493ab8b |
completed | March 30, 2026, 11:17 p.m. |
Created at: March 30, 2026, 5:21 p.m.