Triple
T2027792
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Capernaum |
E44447
|
entity |
| Predicate | religiousSiteFor |
P15993
|
FINISHED |
| Object | Christian pilgrims |
—
|
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: Christian pilgrims | Statement: [Capernaum, religiousSiteFor, Christian pilgrims]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: religiousSiteFor Context triple: [Capernaum, religiousSiteFor, Christian pilgrims]
-
A.
religiousSiteType
Indicates the specific kind or category of religious site associated with an entity (e.g., church, mosque, temple).
-
B.
nearReligiousSite
Indicates that one entity is located close to or in the immediate vicinity of a religious site.
-
C.
isPlaceOfWorshipFor
chosen
Indicates that a location serves as a site where members of a particular religion or belief system perform worship or religious practices.
-
D.
hasReligiousSite
Indicates that a location or entity possesses, contains, or is associated with a religious site such as a temple, church, mosque, shrine, or similar place of worship.
-
E.
religiousTarget
Indicates that an action, policy, or behavior is directed at someone or something specifically because of their religion or religious affiliation.
- 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_69a889144f2481909932f0746a93023d |
completed | March 4, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69abb911e5dc819097e40af0da4d01e7 |
completed | March 7, 2026, 5:35 a.m. |
| PD | Predicate disambiguation | batch_69abb7a656248190ac2ced196b35bc6b |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:38 p.m.