Triple
T31595412
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eparchy of Lungro of the Italo-Albanians |
E806204
|
entity |
| Predicate | hasFaithfulOf |
P99366
|
FINISHED |
| Object | Byzantine Rite |
—
|
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: Byzantine Rite | Statement: [Eparchy of Lungro of the Italo-Albanians, hasFaithfulOf, Byzantine Rite]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFaithfulOf Context triple: [Eparchy of Lungro of the Italo-Albanians, hasFaithfulOf, Byzantine Rite]
-
A.
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.
-
B.
hasFaithfulOfRite
chosen
Indicates that a religious body or authority has adherents who follow a specific liturgical rite.
-
C.
servesFaithfulOf
Indicates that one entity performs services or acts in a ministering or supportive role for those who are faithful to another entity.
-
D.
hasFaithfulCategory
Indicates that one entity is associated with a category functor that is faithful, i.e., it preserves distinct morphisms without identifying them.
-
E.
hasFan
Indicates that an entity is the admirer, supporter, or enthusiast of another entity.
- 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_69f348d4891c8190b02bae3c8ecb68b7 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fcdf2394748190b35cead3e208447d |
completed | May 7, 2026, 6:51 p.m. |
| PD | Predicate disambiguation | batch_69fcdbe344ec8190a0471911952f4b82 |
completed | May 7, 2026, 6:37 p.m. |
Created at: April 30, 2026, 10:30 p.m.