Triple
T29529578
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kaka’i |
E749160
|
entity |
| Predicate | religiousCenterRegions |
P135153
|
FINISHED |
| Object | Kurdistan Region of Iraq |
—
|
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: Kurdistan Region of Iraq | Statement: [Kaka’i, religiousCenterRegions, Kurdistan Region of Iraq]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: religiousCenterRegions Context triple: [Kaka’i, religiousCenterRegions, Kurdistan Region of Iraq]
-
A.
laterReligionRegionOf
Indicates that a region became associated with a particular religion at a later time than another referenced region or context.
-
B.
religiousSiteInRegion
Indicates that a religious site is located within or belongs to a specified geographic region.
-
C.
majorRegionOfWorship
Indicates the primary geographic region where a deity, religion, or cult is predominantly worshipped.
-
D.
devotionalRegion
Indicates the geographic area or region in which a particular devotional practice, cult, or form of worship is observed or centered.
-
E.
regionOfReligiousSignificance
chosen
Indicates that a location or area holds recognized religious importance, such as being sacred, holy, or central to religious practices or beliefs.
- 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_69f0bd46d99c81908ba9d01cc1dbef7d |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_69fdb31800508190beec15adb9bbd292 |
completed | May 8, 2026, 9:55 a.m. |
| PD | Predicate disambiguation | batch_69fdb19c381c8190bafb2f565da097f1 |
completed | May 8, 2026, 9:49 a.m. |
Created at: April 28, 2026, 4:51 p.m.