Triple
T5468760
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Errancis Cemetery |
E122777
|
entity |
| Predicate | burialsTransferred |
P40366
|
FINISHED |
| Object | remains later moved to Paris catacombs (probable) |
—
|
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: remains later moved to Paris catacombs (probable) | Statement: [Errancis Cemetery, burialsTransferred, remains later moved to Paris catacombs (probable)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: burialsTransferred Context triple: [Errancis Cemetery, burialsTransferred, remains later moved to Paris catacombs (probable)]
-
A.
laterBurialsMovedTo
chosen
Indicates that burials that occurred at a later time were relocated from their original site to another place.
-
B.
hasBurialsFrom
Indicates that a location or site contains burials originating from a specified time period, culture, or source.
-
C.
hasBurialsOf
Indicates that a location or site contains or includes the burial places of certain individuals or groups.
-
D.
burials
Indicates that one entity is interred or laid to rest in a grave or burial site associated with another entity.
-
E.
numberOfBurials
Indicates the total count of burial events associated with a given entity.
- 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_69bd4643f16081908d7f29e08096115a |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd927c946c8190aef40679199fede3 |
completed | March 20, 2026, 6:31 p.m. |
| PD | Predicate disambiguation | batch_69bd91a370a88190b5d17b8a5387138d |
completed | March 20, 2026, 6:27 p.m. |
Created at: March 20, 2026, 2:09 p.m.