Triple
T1983744
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coptic Orthodox Church |
E43089
|
entity |
| Predicate | hasMartyrdomTradition |
P1186
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Coptic Orthodox Church, hasMartyrdomTradition, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMartyrdomTradition Context triple: [Coptic Orthodox Church, hasMartyrdomTradition, yes]
-
A.
martyrdomStatus
Indicates the state or condition of an entity with respect to being recognized or regarded as a martyr.
-
B.
hasTraditionIn
Indicates that a particular tradition, custom, or longstanding practice is present, observed, or established within a specified place, group, or context.
-
C.
traditionallyDiedIn
Indicates that, according to tradition or customary accounts (rather than strictly verified historical evidence), one entity is said to have died in the location or context of another entity.
-
D.
hasRiteOrTradition
chosen
Indicates that an entity is associated with, practices, or observes a particular rite, ritual, or tradition.
-
E.
methodOfPersecution
Indicates the specific means, technique, or process by which an act of persecution is carried out.
- 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_69a88713ddc88190a969715658ebe7a8 |
completed | March 4, 2026, 7:25 p.m. |
| NER | Named-entity recognition | batch_69abb96f932881908bebfc4176fda7c0 |
completed | March 7, 2026, 5:36 a.m. |
| PD | Predicate disambiguation | batch_69abb798d288819083132cf14605bd02 |
completed | March 7, 2026, 5:28 a.m. |
Created at: March 4, 2026, 7:37 p.m.