Triple
T23511970
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zvenigorod |
E572448
|
entity |
| Predicate | hasArtHeritage |
P140975
|
FINISHED |
| Object | medieval frescoes |
—
|
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: medieval frescoes | Statement: [Zvenigorod, hasArtHeritage, medieval frescoes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasArtHeritage Context triple: [Zvenigorod, hasArtHeritage, medieval frescoes]
-
A.
hasCulturalHeritageOn
chosen
Indicates that one entity possesses, preserves, or is associated with the cultural heritage embodied in another entity.
-
B.
hasHeritage
Indicates that an entity possesses or is associated with a particular cultural, ethnic, or ancestral background.
-
C.
hasHeritageValueFor
Indicates that something possesses cultural, historical, or heritage significance for a particular entity or community.
-
D.
hasArtHistoricalSignificance
Indicates that something holds notable importance or influence within the context of art history.
-
E.
hasHeritageFocus
Indicates that something is primarily concerned with, dedicated to, or centered around heritage-related themes, values, or preservation.
- 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_69e245b5e4208190bac8a6509867e394 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1aa7f583881909e78e8fe2e6e25fe |
completed | April 29, 2026, 6:51 a.m. |
| PD | Predicate disambiguation | batch_69f0621165c08190a0b27b1319733959 |
completed | April 28, 2026, 7:30 a.m. |
Created at: April 17, 2026, 6:07 p.m.