Triple
T25113442
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Potter’s field |
E629058
|
entity |
| Predicate | typicalBurialPractice |
P6490
|
FINISHED |
| Object | mass graves may be used |
—
|
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: mass graves may be used | Statement: [Potter’s field, typicalBurialPractice, mass graves may be used]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalBurialPractice Context triple: [Potter’s field, typicalBurialPractice, mass graves may be used]
-
A.
burialPractice
Indicates the customary methods, rituals, or procedures a group uses to bury or inter their dead.
-
B.
burialCulture
Indicates the cultural practices, norms, or traditions associated with how a person or remains are buried.
-
C.
primaryDenominationOfBurials
Indicates the main religious denomination associated with the majority of burials at a given burial site or cemetery.
-
D.
hasBurialCustoms
Indicates that a group, culture, or society practices specific rituals or customs related to the treatment and burial of the dead.
-
E.
hasTypeOfBurial
chosen
Indicates the specific kind or method of burial associated with an 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_69e2ff3169d08190973b6061d5009abd |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f78fd5a6388190bfda4bbb2e222e5b |
completed | May 3, 2026, 6:11 p.m. |
| PD | Predicate disambiguation | batch_69f78e2ac3fc819081a45c6841375c8d |
completed | May 3, 2026, 6:04 p.m. |
Created at: April 18, 2026, 6:27 a.m.