Triple
T35884610
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Church of the Virgin of Ljeviša |
E1037604
|
entity |
| Predicate | UNESCOEndangeredListingYear |
P122939
|
FINISHED |
| Object | 2006 |
—
|
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: 2006 | Statement: [Church of the Virgin of Ljeviša, UNESCOEndangeredListingYear, 2006]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: UNESCOEndangeredListingYear Context triple: [Church of the Virgin of Ljeviša, UNESCOEndangeredListingYear, 2006]
-
A.
UNESCOEndangermentCategory
Indicates the level of endangerment assigned to a language according to UNESCO’s classification system.
-
B.
UNESCOTransferYear
Indicates the year in which responsibility, ownership, or designation of something was formally transferred under the authority or framework of UNESCO.
-
C.
UNESCOdangerListInscriptionYear
chosen
Indicates the year in which a site was inscribed on UNESCO’s List of World Heritage in Danger.
-
D.
yearOfUNESCORecognition
Indicates the specific year in which something was officially recognized or inscribed by UNESCO.
-
E.
inscribedOnUNESCOListInYear
Indicates that an entity was officially added to a UNESCO list (such as World Heritage) in a specified year.
- 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_69f76e1f4d748190bb55594d8441d70e |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7aa3883d48190b05e3d2da7a017ae |
completed | May 3, 2026, 8:04 p.m. |
| PD | Predicate disambiguation | batch_69f7a8d435288190b30b1991fb003121 |
completed | May 3, 2026, 7:58 p.m. |
Created at: May 3, 2026, 4:06 p.m.