Triple
T6113125
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Madame Élisabeth of France |
E136292
|
entity |
| Predicate | burialNote |
P21273
|
FINISHED |
| Object | remains later lost after closure of Cimetière des Errancis |
—
|
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 lost after closure of Cimetière des Errancis | Statement: [Madame Élisabeth of France, burialNote, remains later lost after closure of Cimetière des Errancis]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: burialNote Context triple: [Madame Élisabeth of France, burialNote, remains later lost after closure of Cimetière des Errancis]
-
A.
burialText
chosen
Indicates that a text is inscribed on, associated with, or used in connection with a burial or funerary context.
-
B.
burialBy
Indicates that one entity is responsible for burying or interring another entity.
-
C.
burialPlace
Indicates the location where a person or entity is buried.
-
D.
burialStatus
Indicates the state or condition of whether and how an entity has been buried.
-
E.
possiblyBurialOf
Indicates that one entity is a potential or uncertain burial site, grave, or interment location associated with another 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_69c0089ea6f88190b349be53e04b4f5f |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c05bbf2ee4819097af2cce9248bf4e |
completed | March 22, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69c049f80e2081909b7d84a104cda68d |
completed | March 22, 2026, 7:58 p.m. |
Created at: March 22, 2026, 4:14 p.m.