Triple
T28830531
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Qochanis |
E728036
|
entity |
| Predicate | usedByReligiousOrganization |
P56479
|
FINISHED |
| Object | Assyrian Church of the East |
—
|
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: Assyrian Church of the East | Statement: [Qochanis, usedByReligiousOrganization, Assyrian Church of the East]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedByReligiousOrganization Context triple: [Qochanis, usedByReligiousOrganization, Assyrian Church of the East]
-
A.
hasReligiousOrganization
Indicates that an entity is associated with, governed by, or belongs to a specific religious organization.
-
B.
isUsedByReligion
chosen
Indicates that something (such as an object, practice, text, or symbol) is employed or utilized within the context of a particular religion.
-
C.
isInUseForWorship
Indicates that something is currently being used for religious or worship-related activities.
-
D.
usedReligionFor
Indicates that an entity employed religion as a means or tool to achieve some purpose, goal, or effect.
-
E.
declaredReligiousMissionPlace
Indicates that an entity has formally stated or designated a particular place as the location or focus of its religious mission.
- 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_69f0319dc6088190bbfaa206d40ed74a |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f71f8ee0688190bd025f27993452d3 |
completed | May 3, 2026, 10:12 a.m. |
| PD | Predicate disambiguation | batch_69f71cc405c08190863565609a4c8499 |
completed | May 3, 2026, 10 a.m. |
Created at: April 28, 2026, 6:37 a.m.