Triple
T28571188
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Middle Eastern Christianity |
E723118
|
entity |
| Predicate | religionFamily |
P95184
|
FINISHED |
| Object | Christianity |
—
|
NE NERFINISHED |
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: Christianity | Statement: [Middle Eastern Christianity, religionFamily, Christianity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: religionFamily Context triple: [Middle Eastern Christianity, religionFamily, Christianity]
-
A.
orderReligiousFamily
Indicates a relationship where a religious order is affiliated with, belongs to, or is part of a broader religious family or tradition.
-
B.
religiousFamilyBackground
Indicates that two entities are related through a shared or specified religious family upbringing or heritage.
-
C.
fatherReligion
Indicates the religious affiliation or belief system practiced or identified with by a person's father.
-
D.
associatedReligiousFamily
chosen
Indicates a relationship where an entity is linked or connected to a particular religious family or tradition.
-
E.
subjectReligion
Indicates that the subject is associated with, practices, or adheres to a particular religion.
- 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_69f01d7e97708190ae9e77ee66a68abd |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69fd474b7e788190a9bb9b542d878f60 |
completed | May 8, 2026, 2:15 a.m. |
| PD | Predicate disambiguation | batch_69fd46d8b2f0819099d92d72c902f60e |
completed | May 8, 2026, 2:13 a.m. |
Created at: April 28, 2026, 4:10 a.m.