Triple
T23014733
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mamre |
E572999
|
entity |
| Predicate | wasPilgrimageCenterIn |
P150682
|
FINISHED |
| Object | Roman period |
—
|
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: Roman period | Statement: [Mamre, wasPilgrimageCenterIn, Roman period]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasPilgrimageCenterIn Context triple: [Mamre, wasPilgrimageCenterIn, Roman period]
-
A.
isPilgrimageDestination
Indicates that a place serves as a destination specifically visited by people undertaking a religious or spiritual pilgrimage.
-
B.
isPlaceOfPilgrimageFor
Indicates that a location serves as a destination for religious or spiritual pilgrimage for a person or group.
-
C.
hasPilgrimageChurch
Indicates that a location or entity possesses or is associated with a church that serves as a destination for religious pilgrimage.
-
D.
isMajorPilgrimageSite
Indicates that a location is recognized as a primary or highly significant destination for religious pilgrimage.
-
E.
containsNotablePilgrimageCentre
Indicates that a place includes within its boundaries a significant pilgrimage center recognized for religious or spiritual journeys.
- F. None of above. chosen
Provenance (4 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_69e245b764cc8190a51be76f1d9611e1 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f183e3c0e08190a7ac747b056ec3ca |
completed | April 29, 2026, 4:06 a.m. |
| PD | Predicate disambiguation | batch_69ef3b9cd5488190bcd23183179f48cd |
completed | April 27, 2026, 10:34 a.m. |
| PDg | Predicate description generation | batch_69ef538b29c081908fa56ee35a1dcee7 |
completed | April 27, 2026, 12:16 p.m. |
Created at: April 17, 2026, 3:51 p.m.