Triple
T19793369
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mirozhsky Monastery |
E475476
|
entity |
| Predicate | artStyleOfFrescoes |
P108769
|
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: [Mirozhsky Monastery, artStyleOfFrescoes, Byzantine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: artStyleOfFrescoes Context triple: [Mirozhsky Monastery, artStyleOfFrescoes, Byzantine]
-
A.
muralsStyle
Indicates that one entity is a mural whose artistic style or aesthetic is characterized by, derived from, or associated with the other entity.
-
B.
rockArtStyle
Indicates that one entity is characterized by, or associated with, a particular style or tradition of rock art.
-
C.
hasWallPaintingStyle
chosen
Indicates that an entity features or is associated with a particular style or type of wall painting.
-
D.
hasAltarpiecesInStyle
Indicates that an entity possesses or features altarpieces that are created or designed in a specified artistic style.
-
E.
hasFrescoes
Indicates that something contains or is adorned with fresco paintings as part of its structure or decoration.
- 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_69d8e51b014081908b263e167370529a |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e653c4a8a88190afc2f2cd1ebbbe1e |
completed | April 20, 2026, 4:26 p.m. |
| PD | Predicate disambiguation | batch_69e5305858108190bbbfdb9ba3ab9f80 |
completed | April 19, 2026, 7:43 p.m. |
Created at: April 10, 2026, 1:49 p.m.