Triple
T5098857
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Errancis Cemetery |
E114932
|
entity |
| Predicate | primaryInterments |
P25054
|
FINISHED |
| Object | victims of the guillotine |
—
|
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: victims of the guillotine | Statement: [Errancis Cemetery, primaryInterments, victims of the guillotine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryInterments Context triple: [Errancis Cemetery, primaryInterments, victims of the guillotine]
-
A.
firstBurial
Indicates that an entity is the earliest or initial burial associated with a person, place, or burial context.
-
B.
hasBurialsFrom
Indicates that a location or site contains burials originating from a specified time period, culture, or source.
-
C.
burials
chosen
Indicates that one entity is interred or laid to rest in a grave or burial site associated with another entity.
-
D.
numberOfBurials
Indicates the total count of burial events associated with a given entity.
-
E.
hasNotableBurials
Indicates that a place, typically a cemetery or burial site, contains the graves or remains of individuals considered notable or significant.
- 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_69bd443fc49c819089629c00e311310c |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd7568e9c881909f114973faef6832 |
completed | March 20, 2026, 4:27 p.m. |
| PD | Predicate disambiguation | batch_69bd715e06808190931934dc9930f997 |
completed | March 20, 2026, 4:10 p.m. |
Created at: March 20, 2026, 1:40 p.m.