Triple
T33197721
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Collegiate Church of Lirey |
E849811
|
entity |
| Predicate | hasArtifactDisplayed |
P131151
|
FINISHED |
| Object | Shroud of Turin |
—
|
NE NERFINISHED |
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: Shroud of Turin | Statement: [Collegiate Church of Lirey, hasArtifactDisplayed, Shroud of Turin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasArtifactDisplayed Context triple: [Collegiate Church of Lirey, hasArtifactDisplayed, Shroud of Turin]
-
A.
hasArtFormPresented
Indicates that an entity presents, showcases, or features a particular art form.
-
B.
hasSignificantArtifact
Indicates that an entity possesses or is associated with an artifact that is of notable importance, influence, or relevance within a given context.
-
C.
hasCharacteristicArtifact
Indicates that an entity is associated with a specific artifact that characterizes, exemplifies, or is typical of it.
-
D.
hasExhibitElement
Indicates that something (such as an exhibit or display) includes or is composed of a particular element or component.
-
E.
hasWorkOnDisplay
chosen
Indicates that one entity currently has a work or piece being publicly exhibited or shown by 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_69f3495efedc8190843a5728089544b9 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fd7b0503a08190ba07338365b6fcc9 |
completed | May 8, 2026, 5:56 a.m. |
| PD | Predicate disambiguation | batch_69fd7a9733dc81909199f453c0cc2bc1 |
completed | May 8, 2026, 5:54 a.m. |
Created at: May 1, 2026, 1:29 a.m.