Triple
T23807206
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cletus |
E589740
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Early Christian leader |
C17854
|
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: Early Christian leader Context triple: [Cletus, instanceOf, Early Christian leader]
-
A.
1st-century Christian leader
chosen
A 1st-century Christian leader is an influential figure from the earliest decades of the Christian movement who guided communities, taught doctrine, and helped shape the faith’s foundational beliefs and practices.
-
B.
early Christian figure
An early Christian figure is an individual from the first centuries of Christianity who contributed to the formation, spread, or interpretation of the Christian faith through leadership, teaching, writing, or martyrdom.
-
C.
late 5th-century religious leader
A late 5th-century religious leader is an influential spiritual figure who guided the beliefs, practices, and organization of a religious community during the closing decades of the 400s CE.
-
D.
3rd-century Christian bishop
A 3rd-century Christian bishop was a regional church leader responsible for overseeing Christian communities, doctrine, and worship during a period of persecution and theological development in the Roman Empire.
-
E.
4th-century Christian bishop
A 4th-century Christian bishop was a high-ranking church leader responsible for overseeing a Christian community, defending orthodoxy amid theological controversies, and guiding the church through the transition from persecution to imperial favor.
- 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_69e25d19fecc8190a5cf39bbb18d5d7f |
completed | April 17, 2026, 4:17 p.m. |
Created at: April 17, 2026, 7:56 p.m.