Triple
T2189368
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shroud of Turin |
E49825
|
entity |
| Predicate | dateSuggestedByRadiocarbon |
P13262
|
FINISHED |
| Object | between 1260 and 1390 CE |
—
|
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: between 1260 and 1390 CE | Statement: [Shroud of Turin, dateSuggestedByRadiocarbon, between 1260 and 1390 CE]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dateSuggestedByRadiocarbon Context triple: [Shroud of Turin, dateSuggestedByRadiocarbon, between 1260 and 1390 CE]
-
A.
archaeologicalEvidenceAge
Indicates the age or time period to which a piece of archaeological evidence is dated.
-
B.
dateApproximate
Indicates that the associated date is not exact but estimated or approximate rather than precisely known.
-
C.
deciphermentDate
Indicates the date on which something (such as a text, code, or inscription) was successfully deciphered or decoded.
-
D.
discoveryDate
Indicates the date on which something was first discovered or identified.
-
E.
estimatedYearOfCreation
chosen
Indicates the year in which something is believed or approximated to have been created, rather than a precisely known creation year.
- 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_69a88aaba3c48190b351cab9b26989ff |
completed | March 4, 2026, 7:40 p.m. |
| NER | Named-entity recognition | batch_69abbf9e99f08190892d34485c8f2f25 |
completed | March 7, 2026, 6:03 a.m. |
| PD | Predicate disambiguation | batch_69abbda32d1881909d1fd83a751fb21c |
completed | March 7, 2026, 5:54 a.m. |
Created at: March 4, 2026, 7:46 p.m.