Triple
T13171045
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sulaymaniya |
E312974
|
entity |
| Predicate | sharesDoctrinalRootsWith |
P108877
|
FINISHED |
| Object | other Zaydi sub-schools |
—
|
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: other Zaydi sub-schools | Statement: [Sulaymaniya, sharesDoctrinalRootsWith, other Zaydi sub-schools]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sharesDoctrinalRootsWith Context triple: [Sulaymaniya, sharesDoctrinalRootsWith, other Zaydi sub-schools]
-
A.
hasNumberOfDoctrines
Indicates the relationship that specifies how many doctrines are associated with a given entity.
-
B.
hasDoctrinalBasis
Indicates that one concept, claim, or practice is grounded in, supported by, or derived from a specific doctrine or set of doctrines.
-
C.
doctrinalStatus
Indicates the formal standing or classification of a belief, teaching, or doctrine within a particular religious or ideological system.
-
D.
sharesReligionWith
Indicates that two entities follow or are associated with the same religion or religious tradition.
-
E.
doctrinalInfluenceOn
Indicates that one doctrine has influenced, shaped, or contributed to the development of another doctrine.
- F. None of above. chosen
Provenance (4 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_69d806ac3ee081909b2fd27d060aa974 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d98cf054f88190b05ced98d5a22a62 |
completed | April 10, 2026, 11:51 p.m. |
| PD | Predicate disambiguation | batch_69d98bc2c0c88190be357811aa8e828d |
completed | April 10, 2026, 11:46 p.m. |
| PDg | Predicate description generation | batch_69d98ceeb22c8190a6be666031d9e5a4 |
completed | April 10, 2026, 11:51 p.m. |
Created at: April 9, 2026, 9:13 p.m.