Triple
T9855448
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Demonstrations |
E239572
|
entity |
| Predicate | religiousGroupContext |
P9028
|
FINISHED |
| Object | early Syriac church |
—
|
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: early Syriac church | Statement: [Demonstrations, religiousGroupContext, early Syriac church]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: religiousGroupContext Context triple: [Demonstrations, religiousGroupContext, early Syriac church]
-
A.
religiousGroupMentioned
Indicates that a religious group is referenced or mentioned in the given context or statement.
-
B.
religiousCulturalContext
chosen
Indicates the religious or cultural setting, tradition, or framework within which an entity, practice, or event occurs or is interpreted.
-
C.
religiousFoundation
Indicates that an entity was established, created, or founded by a religious organization, authority, or tradition.
-
D.
religiousGroupsPresent
Indicates that one or more religious groups are present or represented in a given context, location, or situation.
-
E.
religiousTarget
Indicates that an action, policy, or behavior is directed at someone or something specifically because of their religion or religious affiliation.
- 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_69ca84e4fdc08190a624425bcef98665 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cdb39719288190adf45e7c029edd51 |
completed | April 2, 2026, 12:08 a.m. |
| PD | Predicate disambiguation | batch_69cd03e57cac8190914bb5ae608a6e0e |
completed | April 1, 2026, 11:39 a.m. |
Created at: March 30, 2026, 8:34 p.m.