Triple
T2033871
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Italo-Albanian Catholic Church |
E44576
|
entity |
| Predicate | belongsToRiteFamily |
P18501
|
FINISHED |
| Object | Greek Byzantine tradition |
—
|
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: Greek Byzantine tradition | Statement: [Italo-Albanian Catholic Church, belongsToRiteFamily, Greek Byzantine tradition]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: belongsToRiteFamily Context triple: [Italo-Albanian Catholic Church, belongsToRiteFamily, Greek Byzantine tradition]
-
A.
belongsToFamily
Indicates that an entity is a member of, or is associated as part of, a specific family group.
-
B.
containsRite
Indicates that one entity includes or incorporates a specific rite as part of its structure, content, or practice.
-
C.
hasLiturgicalFamily
chosen
Indicates that one religious rite, tradition, or practice belongs to, or is classified under, a broader liturgical family or lineage.
-
D.
containsFamily
Indicates that one entity includes or encompasses members of a particular family group within it.
-
E.
hasFamilialTieTo
Indicates a relationship where two entities are connected by family bonds, such as by blood, marriage, or adoption.
- 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_69a889144f2481909932f0746a93023d |
completed | March 4, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69abb93387488190ac9d8d2746451f2e |
completed | March 7, 2026, 5:35 a.m. |
| PD | Predicate disambiguation | batch_69abb7a8125881909c0cb58b777c1faa |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:39 p.m.