Triple
T32132564
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ancient Israelite religion |
E820688
|
entity |
| Predicate | culticCenter |
P88407
|
FINISHED |
| Object | Jerusalem Temple |
—
|
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: Jerusalem Temple | Statement: [Ancient Israelite religion, culticCenter, Jerusalem Temple]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: culticCenter Context triple: [Ancient Israelite religion, culticCenter, Jerusalem Temple]
-
A.
culticFormOf
Indicates that one entity is a religious or ritual expression, manifestation, or practice associated with another entity (such as a deity, belief, or tradition).
-
B.
hasCulticCenter
chosen
Indicates that an entity serves as the primary religious or ritual center associated with another entity.
-
C.
covens
Indicates that one or more entities secretly cooperate or conspire together, often for a shared hidden or illicit purpose.
-
D.
typeOfCult
Indicates that one entity is a specific kind or category of cult relative to another entity.
-
E.
hasCulticPractice
Indicates that an entity engages in, observes, or is associated with a specific religious or ritualistic practice.
- 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_69f349039e0c819091c7a7d322e3f46d |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b9726c848190bd8a36c32c389f2e |
completed | May 3, 2026, 2:56 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a970b0819090c6473844ffa8e3 |
completed | May 3, 2026, 2:32 a.m. |
Created at: May 1, 2026, 12:29 a.m.