Triple
T33197719
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Collegiate Church of Lirey |
E849811
|
entity |
| Predicate | publicDisplayOfShroudStart |
P26941
|
FINISHED |
| Object | 1350s |
—
|
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: 1350s | Statement: [Collegiate Church of Lirey, publicDisplayOfShroudStart, 1350s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: publicDisplayOfShroudStart Context triple: [Collegiate Church of Lirey, publicDisplayOfShroudStart, 1350s]
-
A.
unveiledWith
Indicates that one entity is revealed, introduced, or made public at the same time as, and in conjunction with, another entity.
-
B.
holyRelicDisplayedOn
Indicates that a sacred or revered religious object is being publicly shown or exhibited on a particular surface, structure, or location.
-
C.
unveiledInPresenceOf
Indicates that something was formally revealed or made public while specific other entities were present.
-
D.
reunveiledOn
Indicates that something was revealed or made publicly known again on a specific date or occasion.
-
E.
timeOfFirstRevelation
chosen
Indicates the specific time at which the first revelation or initial disclosure of something occurred.
- 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_69f3495efedc8190843a5728089544b9 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69feecf1bb248190ba30f0bb1d22ee08 |
completed | May 9, 2026, 8:14 a.m. |
| PD | Predicate disambiguation | batch_69feea5f27748190b223ee4e3ba5a678 |
completed | May 9, 2026, 8:03 a.m. |
Created at: May 1, 2026, 1:29 a.m.