Triple
T35931550
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Latin bishopric of Tripoli |
E1039176
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Crusader ecclesiastical see |
C47897
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: Crusader ecclesiastical see Context triple: [Latin bishopric of Tripoli, instanceOf, Crusader ecclesiastical see]
-
A.
ancient Christian episcopal see
An ancient Christian episcopal see is a historical bishopric that served as the central ecclesiastical jurisdiction and seat of a bishop in the early Christian Church.
-
B.
Crusader state
A Crusader state is a feudal polity established by Western European crusaders in the Eastern Mediterranean and surrounding regions during the medieval Crusades, maintained through military, religious, and political control over conquered territories.
-
C.
Anglican episcopal see
An Anglican episcopal see is the geographical area of jurisdiction and the associated office of a bishop within the Anglican Communion.
-
D.
medieval Christian bishopric
chosen
A medieval Christian bishopric is an ecclesiastical jurisdiction governed by a bishop, encompassing both the spiritual authority over clergy and laity and the temporal control of lands, revenues, and often political influence within a defined region.
-
E.
Syriac Orthodox episcopal see
A Syriac Orthodox episcopal see is a territorial jurisdiction of the Syriac Orthodox Church overseen by a bishop, encompassing the administration of clergy, parishes, and liturgical life within its defined region.
- F. None of above.
Provenance (1 batch)
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_69f76e23e4688190a5369138755138bf |
completed | May 3, 2026, 3:47 p.m. |
Created at: May 3, 2026, 4:07 p.m.