Triple
T25409134
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boyko region |
E636639
|
entity |
| Predicate | riteTraditionally |
P3090
|
FINISHED |
| Object | Byzantine Rite |
—
|
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: Byzantine Rite | Statement: [Boyko region, riteTraditionally, Byzantine Rite]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: riteTraditionally Context triple: [Boyko region, riteTraditionally, Byzantine Rite]
-
A.
writingTradition
Indicates a relationship where an entity is associated with, follows, or belongs to a particular system or style of written expression or script usage.
-
B.
rite
chosen
Indicates a ceremonial or ritual action performed according to established traditions or religious practices.
-
C.
traditionalWritingStatus
Indicates the status or condition of something with respect to its use of traditional writing forms or scripts.
-
D.
readingTradition
Indicates a relationship where a text, work, or practice is transmitted, interpreted, and maintained through an established history of readings or interpretive practices.
-
E.
traditionalText
Indicates that the associated text is expressed in a traditional or historically established form, style, or script as opposed to a modern or simplified variant.
- 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_69e75db361d881908d8701c856da6413 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5b00d2924819082adfdfea936a4ef |
completed | May 2, 2026, 8:04 a.m. |
| PD | Predicate disambiguation | batch_69f45d0dbc8c8190beecce679fce90a4 |
completed | May 1, 2026, 7:58 a.m. |
Created at: April 21, 2026, 1:52 p.m.