Triple
T33717681
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Church of St. George (Al-Khader) |
E863920
|
entity |
| Predicate | sharedByCommunities |
P7159
|
FINISHED |
| Object | Christian community |
—
|
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: Christian community | Statement: [Church of St. George (Al-Khader), sharedByCommunities, Christian community]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sharedByCommunities Context triple: [Church of St. George (Al-Khader), sharedByCommunities, Christian community]
-
A.
sharesCommunityWith
Indicates that two entities belong to or participate in the same community or communal group.
-
B.
usedByCommunity
chosen
Indicates that something is utilized or adopted collectively by a particular community.
-
C.
collaboratingCommunity
Indicates that two or more entities are actively working together toward shared goals or projects as part of a community relationship.
-
D.
associatedCommunity
Indicates a relationship where an entity is linked or connected to a particular community with which it is involved or identified.
-
E.
includesCommunitiesFrom
Indicates that one entity encompasses or contains communities that originate from or belong to another entity.
- 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_69f34989871c81908682e22a2fe4b829 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69ffb5c373948190a6606e8caa87a384 |
completed | May 9, 2026, 10:31 p.m. |
| PD | Predicate disambiguation | batch_69ffb261da788190b41399df8ed895e8 |
completed | May 9, 2026, 10:17 p.m. |
Created at: May 1, 2026, 1:44 a.m.