Triple
T34127615
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Washington Parish Burial Ground |
E875331
|
entity |
| Predicate | cemeteryLayout |
P101810
|
FINISHED |
| Object | grid of burial plots with walkways |
—
|
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: grid of burial plots with walkways | Statement: [Washington Parish Burial Ground, cemeteryLayout, grid of burial plots with walkways]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cemeteryLayout Context triple: [Washington Parish Burial Ground, cemeteryLayout, grid of burial plots with walkways]
-
A.
cemeteryStyle
chosen
Indicates the stylistic or design characteristics that define how a cemetery is arranged or presented.
-
B.
cemeteryType
Indicates the specific kind or classification of a cemetery associated with an entity.
-
C.
cemeteryComplex
Indicates a relationship where a site or structure functions as, or is part of, a cemetery complex used for burials or memorials.
-
D.
cemeteryArea
Indicates that an area or region is designated, used, or recognized as a cemetery.
-
E.
cemeterySection
Indicates that one entity is a specific section, area, or subdivision within a cemetery associated with the other entity.
- 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_69f349aa33848190a2e6c5e4533c8444 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f70fb4f18c819099ef6d9177b7d205 |
completed | May 3, 2026, 9:04 a.m. |
| PD | Predicate disambiguation | batch_69f70f3a54d481909ba6bdda3647b761 |
completed | May 3, 2026, 9:02 a.m. |
Created at: May 1, 2026, 1:53 a.m.