Triple
T26613939
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Moračani |
E668005
|
entity |
| Predicate | monasteryReligion |
P158195
|
FINISHED |
| Object | Serbian Orthodox Church |
—
|
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: Serbian Orthodox Church | Statement: [Moračani, monasteryReligion, Serbian Orthodox Church]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: monasteryReligion Context triple: [Moračani, monasteryReligion, Serbian Orthodox Church]
-
A.
monasteryDenomination
chosen
Indicates the religious denomination or order with which a monastery is affiliated.
-
B.
monastery
Indicates that an entity is or functions as a monastery, typically a religious community or building where monastics live and practice.
-
C.
monasteryType
Indicates the specific kind or classification of a monastery in relation to its broader religious or organizational category.
-
D.
monasteriesAre
Indicates that a subject is classified as, functions as, or is identified with monasteries.
-
E.
monasteryDedicatedTo
Indicates that a monastery is formally devoted or consecrated to a particular deity, saint, religious figure, or sacred concept.
- 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_69ee9cfe16088190a3dddd68e3c7b1ea |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69f61a17a7788190946f7e32d63cd43f |
completed | May 2, 2026, 3:36 p.m. |
| PD | Predicate disambiguation | batch_69f611ab768c8190b1849c15a3e59dda |
completed | May 2, 2026, 3 p.m. |
Created at: April 27, 2026, 2:17 a.m.