Triple
T28725162
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Besalú |
E730201
|
entity |
| Predicate | hasJewishSite |
P916
|
FINISHED |
| Object | medieval mikveh |
—
|
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: medieval mikveh | Statement: [Besalú, hasJewishSite, medieval mikveh]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasJewishSite Context triple: [Besalú, hasJewishSite, medieval mikveh]
-
A.
hasJewishInstitution
Indicates that a place, organization, or entity possesses, hosts, or is associated with a Jewish religious, cultural, or educational institution.
-
B.
hasJewishDenomination
Indicates that an entity is associated with, or belongs to, a specific Jewish religious denomination or movement.
-
C.
hasSignificantJewishCommunity
Indicates that a place or entity possesses a notably large, influential, or historically important Jewish community.
-
D.
hasSynagogueType
Indicates the specific classification or type of synagogue associated with an entity.
-
E.
hasReligiousSite
chosen
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.
- 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_69f043e91fe48190b73bcd8e08d433e0 |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69f6570caa888190b05d9aa932648185 |
completed | May 2, 2026, 7:57 p.m. |
| PD | Predicate disambiguation | batch_69f651ac855481908e30c3b345d31356 |
completed | May 2, 2026, 7:34 p.m. |
Created at: April 28, 2026, 5:55 a.m.