Triple
T36754094
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Khonj |
E907997
|
entity |
| Predicate | hasMinorityReligionContext |
P2812
|
FINISHED |
| Object | Shia-majority region |
—
|
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: Shia-majority region | Statement: [Khonj, hasMinorityReligionContext, Shia-majority region]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMinorityReligionContext Context triple: [Khonj, hasMinorityReligionContext, Shia-majority region]
-
A.
hasMinorityChurch
Indicates that a church or religious group exists in a given place but represents a minority compared to other religious affiliations there.
-
B.
religionMinority
chosen
Indicates that the subject’s religion is a minority faith within the relevant population or context.
-
C.
hasSecondaryReligion
Indicates that an entity practices, adheres to, or is associated with a secondary religion in addition to its primary religion.
-
D.
religionSignificantMinorityRegion
Indicates that a particular religion constitutes a significant minority presence within a specified geographic region.
-
E.
hasMinorityIn
Indicates that one entity holds a non-controlling, minority ownership or stake in 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_69f76e779bec8190be0e1f87a131e0f4 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fd5bf69acc819092a01e4259785dc3 |
completed | May 8, 2026, 3:43 a.m. |
| PD | Predicate disambiguation | batch_69fd59b3f4ac8190a7f9dd3142da6e09 |
completed | May 8, 2026, 3:34 a.m. |
Created at: May 3, 2026, 4:12 p.m.