Triple
T9625086
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chieveley Military Cemetery, KwaZulu-Natal, South Africa |
E232439
|
entity |
| Predicate | hasBurialDateRange |
P45931
|
FINISHED |
| Object | circa 1899–1900 |
—
|
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: circa 1899–1900 | Statement: [Chieveley Military Cemetery, KwaZulu-Natal, South Africa, hasBurialDateRange, circa 1899–1900]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBurialDateRange Context triple: [Chieveley Military Cemetery, KwaZulu-Natal, South Africa, hasBurialDateRange, circa 1899–1900]
-
A.
dateOfBurial
Indicates the specific date on which an entity was buried.
-
B.
hasBurialsFrom
chosen
Indicates that a location or site contains burials originating from a specified time period, culture, or source.
-
C.
burialsUntil
Indicates the number of burial events that remain or are scheduled to occur up to a specified point in time or condition.
-
D.
hasBurialsOf
Indicates that a location or site contains or includes the burial places of certain individuals or groups.
-
E.
hasBurialEligibility
Indicates that one entity is permitted or qualified to be buried in a particular place, context, or under specified conditions.
- 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_69ca848793ec8190a93a12383a754dc0 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9afb67c88190aa170716f0033752 |
completed | April 1, 2026, 10:23 p.m. |
| PD | Predicate disambiguation | batch_69ccd5aa1d2c8190a287bf1cf4a3037e |
completed | April 1, 2026, 8:22 a.m. |
Created at: March 30, 2026, 8:10 p.m.