Triple
T36966982
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coptic Egypt |
E914457
|
entity |
| Predicate | hasCoreReligiousTradition |
P27867
|
FINISHED |
| Object | Coptic Christianity |
E1493911
|
NE 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: Coptic Christianity | Statement: [Coptic Egypt, hasCoreReligiousTradition, Coptic Christianity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCoreReligiousTradition Context triple: [Coptic Egypt, hasCoreReligiousTradition, Coptic Christianity]
-
A.
partOfReligiousTradition
Indicates that one entity belongs to, is included within, or is practiced as a component of a particular religious tradition.
-
B.
hasReligiousOrigin
Indicates that something originates from, is derived from, or is fundamentally based on a religious tradition, belief system, or practice.
-
C.
hasPrimaryReligionComplex
Indicates that an entity is primarily associated with, practices, or is characterized by a particular religion or religious complex.
-
D.
hasReligious
Indicates that an entity is associated with, practices, or adheres to a particular religion or religious affiliation.
-
E.
hasAssociatedReligion
chosen
Indicates that an entity is connected with or linked to a particular religion.
- F. None of above.
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_69f76e8c498c8190b2842db80aea8b3b |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a037c8e2c648190a65fc9c7872861af |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3e2c42186081909abbd5f5fadf94d7 |
completed | June 26, 2026, 7:37 a.m. |
| PD | Predicate disambiguation | batch_6a037a10036481909c71188b2a0e7f04 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:14 p.m.