Triple
T30617705
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | שִׁלֹה |
E779357
|
entity |
| Predicate | timeAsReligiousCenter |
P23109
|
FINISHED |
| Object | period of Judges |
—
|
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: period of Judges | Statement: [שִׁלֹה, timeAsReligiousCenter, period of Judges]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeAsReligiousCenter Context triple: [שִׁלֹה, timeAsReligiousCenter, period of Judges]
-
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.
tookPlaceAtReligiousCenter
Indicates that an event or action occurred at a religious center or place of worship.
-
C.
ecclesiasticalCenter
chosen
Indicates that a place functions as a primary religious or church administrative hub for a surrounding area or community.
-
D.
foundedAsReligiousSiteInCentury
Indicates that something was originally established as a religious site during a specified century.
-
E.
hasReligiousSignificanceVia
Indicates that something holds religious significance specifically by means of, or through the mediation of, another entity, event, or context.
- 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_69f224a3307081909a6dca8ca75dbf48 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f68a16debc8190a12f5f65ced055d7 |
completed | May 2, 2026, 11:34 p.m. |
| PD | Predicate disambiguation | batch_69f6860def1c81909d79e1f088c4b5e5 |
completed | May 2, 2026, 11:17 p.m. |
Created at: April 29, 2026, 8:26 p.m.