Triple
T34782128
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kafr Kanna |
E1002695
|
entity |
| Predicate | hasChristianSiteType |
P45953
|
FINISHED |
| Object | church |
—
|
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: church | Statement: [Kafr Kanna, hasChristianSiteType, church]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasChristianSiteType Context triple: [Kafr Kanna, hasChristianSiteType, church]
-
A.
hasChurchType
chosen
Indicates that one entity (typically a church) is classified as being of a particular church type or category.
-
B.
isTypeSiteOf
Indicates that a site serves as the specific location or setting where a particular type, category, or classification is realized or occurs.
-
C.
hasReligiousInstitutionType
Indicates that an entity is associated with, or classified by, a specific type of religious institution.
-
D.
hasProductionSiteType
Indicates that an entity has a production site characterized by a specific type or category of production facility.
-
E.
hasReligiousSite
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_69f76db30a108190bb57ca95b873e5bb |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69fea1f5d8c481908dc3351dc9ecef7f |
completed | May 9, 2026, 2:54 a.m. |
| PD | Predicate disambiguation | batch_69fea06b6fe0819095bf4c1bc9809927 |
completed | May 9, 2026, 2:48 a.m. |
Created at: May 3, 2026, 3:59 p.m.