Triple
T23576359
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sanz-Klausenburg |
E580266
|
entity |
| Predicate | countryOfReligiousCenter |
P55124
|
FINISHED |
| Object | Israel |
—
|
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: Israel | Statement: [Sanz-Klausenburg, countryOfReligiousCenter, Israel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: countryOfReligiousCenter Context triple: [Sanz-Klausenburg, countryOfReligiousCenter, Israel]
-
A.
regionOfReligiousSignificance
Indicates that a location or area holds recognized religious importance, such as being sacred, holy, or central to religious practices or beliefs.
-
B.
hasReligiousHeadquarters
chosen
Indicates that an organization or religious group has its main religious administrative center or headquarters located at a specific place.
-
C.
ecclesiasticalCenter
Indicates that a place functions as a primary religious or church administrative hub for a surrounding area or community.
-
D.
countryOfVeneration
Indicates the country in which a person, figure, or entity is formally or traditionally venerated or honored.
-
E.
countryOfMainRitual
Indicates the country in which a given ritual is primarily performed or holds its main significance.
- 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_69e24601a9108190bc31e83833c980e4 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f1afd6608481909a0d293ba8f65b2b |
completed | April 29, 2026, 7:14 a.m. |
| PD | Predicate disambiguation | batch_69f118bcc0b08190b25a8dddfd461a0e |
completed | April 28, 2026, 8:29 p.m. |
Created at: April 17, 2026, 6:38 p.m.