Triple
T11109185
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eparchy of Lugoj |
E262709
|
entity |
| Predicate | religiousRiteFamily |
P18501
|
FINISHED |
| Object | Byzantine |
—
|
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 | Statement: [Eparchy of Lugoj, religiousRiteFamily, Byzantine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: religiousRiteFamily Context triple: [Eparchy of Lugoj, religiousRiteFamily, Byzantine]
-
A.
associatedReligiousFamily
Indicates a relationship where an entity is linked or connected to a particular religious family or tradition.
-
B.
religiousOrRitualAssociation
Indicates a connection between entities based on shared religious, spiritual, or ritual practices, roles, or significance.
-
C.
hasLiturgicalFamily
chosen
Indicates that one religious rite, tradition, or practice belongs to, or is classified under, a broader liturgical family or lineage.
-
D.
religiousFunction
Indicates that one entity serves a religious role, purpose, or function in relation to another entity.
-
E.
religiousBranchOf
Indicates that one religion, denomination, or sect is a subdivision or offshoot of a larger parent religious tradition.
- 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_69d6aa9b46cc8190b19f9f0cc45bf322 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d79a6896c0819082685b5b4600d158 |
completed | April 9, 2026, 12:24 p.m. |
| PD | Predicate disambiguation | batch_69d7441cf8188190b8095f622c923156 |
completed | April 9, 2026, 6:15 a.m. |
Created at: April 8, 2026, 9:27 p.m.