Triple
T27749780
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brythonic kingdom of Bryneich |
E702085
|
entity |
| Predicate | religionPossibly |
P81268
|
FINISHED |
| Object | early Christianity |
—
|
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: early Christianity | Statement: [Brythonic kingdom of Bryneich, religionPossibly, early Christianity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: religionPossibly Context triple: [Brythonic kingdom of Bryneich, religionPossibly, early Christianity]
-
A.
religionOrBelief
Indicates that one entity holds, practices, or is associated with a particular religion, faith, or belief system.
-
B.
subjectReligion
Indicates that the subject is associated with, practices, or adheres to a particular religion.
-
C.
majorReligionCanBe
chosen
Indicates that an entity can have a particular major religion as one of its possible primary religious affiliations.
-
D.
bearerReligion
Indicates that a bearer (such as a person or entity) adheres to, practices, or is associated with a particular religion.
-
E.
religionCommon
Indicates that the related entities share the same 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_69ef6a53c7388190899baa6daf42301c |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69fce28d6c3081908bf76f5db63ecf68 |
completed | May 7, 2026, 7:05 p.m. |
| PD | Predicate disambiguation | batch_69fce12d2f08819082134b5eb3db6a24 |
completed | May 7, 2026, 6:59 p.m. |
Created at: April 27, 2026, 4:19 p.m.