Triple
T36257199
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alan D. Adler |
E891970
|
entity |
| Predicate | religiousArtifactStudied |
P128939
|
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: [Alan D. Adler, religiousArtifactStudied, Shroud of Turin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: religiousArtifactStudied Context triple: [Alan D. Adler, religiousArtifactStudied, Shroud of Turin]
-
A.
relicsAssociatedWith
Indicates a relationship where certain relics are connected or linked to a particular entity, context, or subject (such as a person, place, event, or tradition).
-
B.
associatedReligionForRelic
Indicates the religion with which a particular relic is associated.
-
C.
holyRelicDisplayedOn
Indicates that a sacred or revered religious object is being publicly shown or exhibited on a particular surface, structure, or location.
-
D.
hasReligiousObject
chosen
Indicates that an entity possesses, is associated with, or contains a religious object (such as an artifact, symbol, or item used in religious practice).
-
E.
relicsDiscoveryYear
Indicates the year in which the relics were discovered.
- 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_69f76e4599108190811532e707d6bc2c |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69ffe613c03481909f3043ec8bf0bed9 |
completed | May 10, 2026, 1:57 a.m. |
| PD | Predicate disambiguation | batch_69ffe4a73fb4819091600725a443981a |
completed | May 10, 2026, 1:51 a.m. |
Created at: May 3, 2026, 4:09 p.m.