Triple
T28180882
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Antelias |
E716021
|
entity |
| Predicate | hasReligiousCouncil |
P65910
|
FINISHED |
| Object | Synod of the Great House of Cilicia |
—
|
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: Synod of the Great House of Cilicia | Statement: [Antelias, hasReligiousCouncil, Synod of the Great House of Cilicia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasReligiousCouncil Context triple: [Antelias, hasReligiousCouncil, Synod of the Great House of Cilicia]
-
A.
religiousCouncil
chosen
Indicates a formal gathering or assembly convened to deliberate, decide, or issue guidance on religious doctrines, practices, or governance.
-
B.
hasReligiousOrganization
Indicates that an entity is associated with, governed by, or belongs to a specific religious organization.
-
C.
isRuledByClergy
Indicates that a group, region, or institution is governed or controlled by members of a religious clergy.
-
D.
hasClergy
Indicates that an organization or institution possesses or is served by members of the clergy.
-
E.
hasReligious
Indicates that an entity is associated with, practices, or adheres to a particular 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_69efd6b4fc5c81909dd88f01a8c2b35d |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_69ff370698ec81909bb1596d7d4112ba |
completed | May 9, 2026, 1:30 p.m. |
| PD | Predicate disambiguation | batch_69ff3699b6288190b564839cb05f5cf6 |
completed | May 9, 2026, 1:28 p.m. |
Created at: April 27, 2026, 10:19 p.m.