Triple
T23856770
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dieweg Cemetery |
E592330
|
entity |
| Predicate | usedAsMainCemeteryOf |
P154210
|
FINISHED |
| Object | Uccle |
—
|
NE NERFINISHED |
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: Uccle | Statement: [Dieweg Cemetery, usedAsMainCemeteryOf, Uccle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedAsMainCemeteryOf Context triple: [Dieweg Cemetery, usedAsMainCemeteryOf, Uccle]
-
A.
isLargestCemeteryOf
Indicates that one cemetery is the largest (by size, capacity, or another defined measure) among all cemeteries associated with a given place or entity.
-
B.
hasCemetery
Indicates that one entity possesses, contains, or includes a cemetery associated with it.
-
C.
usedAsCemeterySince
Indicates that a place has functioned as a cemetery starting from a specified point in time.
-
D.
hasNotablePeriodOfUseAsCemetery
Indicates that something was significantly used as a cemetery during a particular period of time.
-
E.
usedAsBurialGroundUntil
Indicates that a place functioned as a burial ground up to a specified end time or date.
- 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_69e25d22eb488190914b193aff952e83 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1c98b29a881909eb60c1be1acdbe9 |
completed | April 29, 2026, 9:04 a.m. |
| PD | Predicate disambiguation | batch_69f1614612b481908c45d99e588882f9 |
completed | April 29, 2026, 1:39 a.m. |
| PDg | Predicate description generation | batch_69f16e348b548190b76e50f9b611f76d |
completed | April 29, 2026, 2:34 a.m. |
Created at: April 17, 2026, 8:12 p.m.