Triple
T34512745
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sancta Camisa |
E886066
|
entity |
| Predicate | isMajorPilgrimageRelicAt |
P156867
|
FINISHED |
| Object | Chartres Cathedral |
—
|
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: Chartres Cathedral | Statement: [Sancta Camisa, isMajorPilgrimageRelicAt, Chartres Cathedral]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isMajorPilgrimageRelicAt Context triple: [Sancta Camisa, isMajorPilgrimageRelicAt, Chartres Cathedral]
-
A.
isMajorPilgrimageSite
Indicates that a location is recognized as a primary or highly significant destination for religious pilgrimage.
-
B.
isPilgrimageDestination
Indicates that a place serves as a destination specifically visited by people undertaking a religious or spiritual pilgrimage.
-
C.
hasPilgrimageObject
Indicates that an entity has a specific object or site that serves as the focus or destination of a pilgrimage associated with it.
-
D.
isPilgrimageStopOn
Indicates that a location serves as a designated stop or waypoint along a particular pilgrimage route.
-
E.
pilgrimageObject
chosen
Indicates that something serves as the destination, focus, or goal of a religious pilgrimage.
- 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_69f349ccc290819089d8e82698e53cb6 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fd8ccbd4c88190b13aae0673b3c821 |
completed | May 8, 2026, 7:12 a.m. |
| PD | Predicate disambiguation | batch_69fd8ae2227c819089546f5c3629799e |
completed | May 8, 2026, 7:04 a.m. |
Created at: May 1, 2026, 2:01 a.m.