Triple
T17712829
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Basilides |
E441612
|
entity |
| Predicate | consideredByEarlyChurch |
P101142
|
FINISHED |
| Object | heretic |
—
|
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: heretic | Statement: [Basilides, consideredByEarlyChurch, heretic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: consideredByEarlyChurch Context triple: [Basilides, consideredByEarlyChurch, heretic]
-
A.
recognizedAsEcumenicalBy
Indicates that a council, decree, or similar religious event is officially acknowledged as ecumenical (universally authoritative for the whole Church) by a specified religious body or tradition.
-
B.
consideredByRomeAs
Indicates that something or someone is regarded or classified in a particular way by Rome (e.g., Roman authorities, culture, or legal system).
-
C.
perceivedByMainstreamChurchesAs
chosen
Indicates that something is regarded or understood in a particular way by mainstream churches.
-
D.
consideredHeresySince
Indicates that something has been officially regarded as heretical starting from a specified point in time.
-
E.
statusAtCouncilOfChalcedon
Indicates the role, standing, or position an entity held at the time of the Council of Chalcedon.
- 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_69d8b9ea20b48190ace88bb46b01e6a9 |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e4729c2c98819086fe48420217308d |
completed | April 19, 2026, 6:13 a.m. |
| PD | Predicate disambiguation | batch_69e3cde601d4819097903f471f1fe99a |
completed | April 18, 2026, 6:31 p.m. |
Created at: April 10, 2026, 10:06 a.m.