Triple
T19951643
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Darkley killings |
E479568
|
entity |
| Predicate | placeOfWorshipType |
P92816
|
FINISHED |
| Object | Pentecostal church |
—
|
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: Pentecostal church | Statement: [Darkley killings, placeOfWorshipType, Pentecostal church]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: placeOfWorshipType Context triple: [Darkley killings, placeOfWorshipType, Pentecostal church]
-
A.
religiousBuildingInstanceOf
chosen
Indicates that a specific religious building is an instance of a particular class or type of religious building.
-
B.
religionBuildingDenomination
Indicates the specific religious denomination with which a religious building is affiliated or to which it belongs.
-
C.
religiousServiceType
Indicates the specific kind or category of religious service associated with an event or context.
-
D.
hasPlaceOfWorship
Indicates that an entity possesses, contains, or is associated with a designated location used for religious or spiritual worship.
-
E.
isPlaceOfWorshipFor
Indicates that a location serves as a site where members of a particular religion or belief system perform worship or religious practices.
- 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_69d8e522a17c819095165d4d24939fd8 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e65a6c87388190a1bada3117acaf7b |
completed | April 20, 2026, 4:55 p.m. |
| PD | Predicate disambiguation | batch_69e537f47c508190853c4e009c6b5566 |
completed | April 19, 2026, 8:15 p.m. |
Created at: April 10, 2026, 1:54 p.m.