Triple
T35552222
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Colonial Park Cemetery |
E1027393
|
entity |
| Predicate | closedToNewBurials |
P95011
|
FINISHED |
| Object | mid-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: mid-19th century | Statement: [Colonial Park Cemetery, closedToNewBurials, mid-19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: closedToNewBurials Context triple: [Colonial Park Cemetery, closedToNewBurials, mid-19th century]
-
A.
isClosedToMostNewInterments
chosen
Indicates that a burial site has largely stopped accepting new interments, allowing only limited or exceptional new burials.
-
B.
burialsUntil
Indicates the number of burial events that remain or are scheduled to occur up to a specified point in time or condition.
-
C.
hasBurialsOf
Indicates that a location or site contains or includes the burial places of certain individuals or groups.
-
D.
cemeteryBurialsSince
Indicates the number of burials that have occurred in a cemetery from a specified point in time onward.
-
E.
hasBurialsFrom
Indicates that a location or site contains burials originating from a specified time period, culture, or source.
- 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_69f76e014fd481909e9f04ac603a2aa9 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fcc7338120819081cb46547d60f2cb |
completed | May 7, 2026, 5:09 p.m. |
| PD | Predicate disambiguation | batch_69fcc58566a0819082d5ea36e03bf0c6 |
completed | May 7, 2026, 5:01 p.m. |
Created at: May 3, 2026, 4:04 p.m.