Triple
T6471898
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Monastery of the Temptation |
E142371
|
entity |
| Predicate | nearBiblicalSite |
P61457
|
FINISHED |
| Object | baptismal area of the Jordan River |
—
|
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: baptismal area of the Jordan River | Statement: [Monastery of the Temptation, nearBiblicalSite, baptismal area of the Jordan River]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nearBiblicalSite Context triple: [Monastery of the Temptation, nearBiblicalSite, baptismal area of the Jordan River]
-
A.
nearReligiousSite
Indicates that one entity is located close to or in the immediate vicinity of a religious site.
-
B.
hasNearbyPilgrimageSite
chosen
Indicates that one entity is located close to a place used as a pilgrimage site for religious or spiritual journeys.
-
C.
notableNearbySite
Indicates that one entity is a significant or noteworthy site located close to another entity.
-
D.
nearGeologicalSite
Indicates that one entity is located in close physical proximity to a geological site or feature.
-
E.
nearbyWorldHeritageSite
Indicates that one entity is located close to, or in the immediate vicinity of, a designated World Heritage Site.
- 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_69c008d3bf4c8190bcf798c5ba9d6fb3 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c06a2fd4248190a789bf0301e2860a |
completed | March 22, 2026, 10:16 p.m. |
| PD | Predicate disambiguation | batch_69c0673d46a08190bc8bcd29f9555fe7 |
completed | March 22, 2026, 10:03 p.m. |
Created at: March 22, 2026, 4:50 p.m.