Triple
T2959997
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gračanica Monastery |
E80021
|
entity |
| Predicate | UNESCOID |
P2117
|
FINISHED |
| Object | 724bis |
—
|
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: 724bis | Statement: [Gračanica Monastery, UNESCOID, 724bis]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: UNESCOID Context triple: [Gračanica Monastery, UNESCOID, 724bis]
-
A.
UNESCORegion
Indicates that an entity is associated with, classified under, or belongs to a specific UNESCO-designated geographic region.
-
B.
UNESCOWorldHeritageSiteId
chosen
Indicates that an entity is identified as a UNESCO World Heritage Site by a specific UNESCO World Heritage Site identifier.
-
C.
UNESCOElement
Indicates that one entity is recognized as an element associated with UNESCO, such as being part of its heritage, cultural, or educational designations.
-
D.
roleWithUNESCO
Indicates that an entity holds or has held an official position, function, or recognized capacity in relation to UNESCO.
-
E.
UNESCOSiteType
Indicates the classification of a UNESCO World Heritage Site according to its type (e.g., cultural, natural, or mixed).
- 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_69ad8b1341848190bd19dbf46892887d |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad992dd4248190b5f3d4f342593b8c |
completed | March 8, 2026, 3:43 p.m. |
| PD | Predicate disambiguation | batch_69ad960c5c8881909d679912bd7d78f3 |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 2:57 p.m.