Triple
T13461504
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gunnersbury Cemetery, London |
E311377
|
entity |
| Predicate | hasCommunityGraves |
P109595
|
FINISHED |
| Object | diverse religious communities |
—
|
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: diverse religious communities | Statement: [Gunnersbury Cemetery, London, hasCommunityGraves, diverse religious communities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCommunityGraves Context triple: [Gunnersbury Cemetery, London, hasCommunityGraves, diverse religious communities]
-
A.
hasCemetery
Indicates that one entity possesses, contains, or includes a cemetery associated with it.
-
B.
hasGraveOrMemorialOf
Indicates that a location or object serves as the grave or memorial site dedicated to a particular person or entity.
-
C.
hasGravesOfCitizenship
Indicates that a place contains graves belonging to individuals of a specified citizenship.
-
D.
hasNearbyCemetery
Indicates that one entity is located close to, or in the immediate vicinity of, a cemetery associated with another entity.
-
E.
hasMassGraveOf
Indicates that a location or site contains a mass grave in which the referenced individuals or remains are buried.
- F. None of above. chosen
Provenance (4 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_69d806a938b8819097ec43a2229fc7f9 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69dbaf0d95fc81909d9f73d5315dc7b4 |
completed | April 12, 2026, 2:41 p.m. |
| PD | Predicate disambiguation | batch_69d9a03dcd0c8190a8927eb4eaad1c45 |
completed | April 11, 2026, 1:13 a.m. |
| PDg | Predicate description generation | batch_69dadce235f88190a6433395d2969811 |
completed | April 11, 2026, 11:44 p.m. |
Created at: April 9, 2026, 9:41 p.m.