Triple
T27629171
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stanimaka |
E696290
|
entity |
| Predicate | associatedWithMonasteries |
P26422
|
FINISHED |
| Object | Bachkovo Monastery |
—
|
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: Bachkovo Monastery | Statement: [Stanimaka, associatedWithMonasteries, Bachkovo Monastery]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithMonasteries Context triple: [Stanimaka, associatedWithMonasteries, Bachkovo Monastery]
-
A.
monasteriesAre
Indicates that a subject is classified as, functions as, or is identified with monasteries.
-
B.
monasteryAffiliation
chosen
Indicates a relationship where an entity is formally associated with, belongs to, or is under the authority of a particular monastery.
-
C.
numberOfMonasteries
Indicates the quantity of monasteries associated with a given entity or within a specified context.
-
D.
inspiredMonasteries
Indicates that one entity served as an inspiration or model for the founding, design, or practices of certain 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_69ef59092c8881908114ad184248cc46 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_6a002dd4066c8190945a09ed82f44f3f |
completed | May 10, 2026, 7:03 a.m. |
| PD | Predicate disambiguation | batch_6a002b141f4081909999e14988105f3a |
completed | May 10, 2026, 6:52 a.m. |
Created at: April 27, 2026, 2:20 p.m.