Triple
T32783591
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ypres Reservoir Cemetery |
E838424
|
entity |
| Predicate | hasApproximateNumberOfIdentifiedBurials |
P148531
|
FINISHED |
| Object | 2300 |
—
|
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: 2300 | Statement: [Ypres Reservoir Cemetery, hasApproximateNumberOfIdentifiedBurials, 2300]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasApproximateNumberOfIdentifiedBurials Context triple: [Ypres Reservoir Cemetery, hasApproximateNumberOfIdentifiedBurials, 2300]
-
A.
numberOfBurials
Indicates the total count of burial events associated with a given entity.
-
B.
hasBurialsOf
Indicates that a location or site contains or includes the burial places of certain individuals or groups.
-
C.
hasBurialsFrom
Indicates that a location or site contains burials originating from a specified time period, culture, or source.
-
D.
hasNotableBurials
Indicates that a place, typically a cemetery or burial site, contains the graves or remains of individuals considered notable or significant.
-
E.
numberOfGravesApproximate
chosen
Indicates that the stated count of graves is an estimated or approximate number rather than an exact figure.
- 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_69f3493b83f48190be335cd42465cecf |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fd0d0ba5c48190bddb3f0e6637544c |
completed | May 7, 2026, 10:07 p.m. |
| PD | Predicate disambiguation | batch_69fd0c4324a8819086c90adf46216e0e |
completed | May 7, 2026, 10:03 p.m. |
Created at: May 1, 2026, 1:14 a.m.