Triple
T36306501
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blessed Methodius Dominic Trčka |
E893954
|
entity |
| Predicate | hasFaith |
P136960
|
FINISHED |
| Object | Christianity |
—
|
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: Christianity | Statement: [Blessed Methodius Dominic Trčka, hasFaith, Christianity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFaith Context triple: [Blessed Methodius Dominic Trčka, hasFaith, Christianity]
-
A.
mainFaith
Indicates that one entity is the primary or predominant religious belief or faith tradition associated with another entity.
-
B.
hasCredo
Indicates that an entity holds, follows, or is characterized by a particular guiding belief, principle, or statement of values.
-
C.
hasReligious
chosen
Indicates that an entity is associated with, practices, or adheres to a particular religion or religious affiliation.
-
D.
hasLayFaithful
Indicates that an entity (typically a religious organization or community) includes or is associated with lay faithful, i.e., non-ordained members of the faith.
-
E.
hasFaithfulOfRite
Indicates that a religious body or authority has adherents who follow a specific liturgical rite.
- 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_69f76e4c1b248190b10667d0213537fe |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fe68a4b67881909ca1d9f276f922e0 |
completed | May 8, 2026, 10:50 p.m. |
| PD | Predicate disambiguation | batch_69fe680234c88190b01f953987b74972 |
completed | May 8, 2026, 10:47 p.m. |
Created at: May 3, 2026, 4:09 p.m.