Triple
T35288848
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oplenac Church |
E1019165
|
entity |
| Predicate | hasMosaicProgram |
P117340
|
FINISHED |
| Object | scenes from Serbian medieval monasteries |
—
|
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: scenes from Serbian medieval monasteries | Statement: [Oplenac Church, hasMosaicProgram, scenes from Serbian medieval monasteries]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMosaicProgram Context triple: [Oplenac Church, hasMosaicProgram, scenes from Serbian medieval monasteries]
-
A.
hasMosaic
Indicates that one entity possesses, contains, or is decorated with a mosaic.
-
B.
hasMosaicsBy
Indicates that something contains or features mosaics that were created by a specified agent or creator.
-
C.
hasMosaicSubject
chosen
Indicates that something is the depicted subject or main theme represented within a mosaic.
-
D.
hasMosaicNameTablet
Indicates that an entity is associated with, or possesses, a tablet that bears the name used in a mosaic.
-
E.
hasProgramCode
Indicates that an entity is associated with a specific program identifier or code used to reference or classify it within a system.
- 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_69f76de6d39c8190bb11342e4b91ff2b |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69ff136ed2a881908f713401083970d1 |
completed | May 9, 2026, 10:58 a.m. |
| PD | Predicate disambiguation | batch_69ff10f9e3448190b6cb6ea5a67713c1 |
completed | May 9, 2026, 10:48 a.m. |
Created at: May 3, 2026, 4:03 p.m.