Triple
T38624871
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Спас на Крови |
E936978
|
entity |
| Predicate | hasMosaicArea |
P201178
|
FINISHED |
| Object | более 7000 м² мозаик |
—
|
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: более 7000 м² мозаик | Statement: [Спас на Крови, hasMosaicArea, более 7000 м² мозаик]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMosaicArea Context triple: [Спас на Крови, hasMosaicArea, более 7000 м² мозаик]
-
A.
hasMacroArea
Indicates that one entity belongs to, or is located within, a broader geographic or conceptual macro-area represented by another entity.
-
B.
hasCollectionArea
Indicates that an entity is associated with a specific geographic or spatial area from which items, specimens, or data are collected.
-
C.
hasProtectedAreaCoverage
Indicates that a specified portion or extent of an area falls within officially designated protected areas.
-
D.
hasIconicArea
Indicates that an entity possesses a distinct, widely recognized area or region that is emblematic or characteristic of it.
-
E.
hasAreaType
Indicates that an entity is associated with a specific kind or classification of area (e.g., urban, rural, coastal).
- F. None of above. chosen
Provenance (4 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_69f76ed403208190b862dc795171353f |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ffcf46fd688190907fd1ceb499a8d1 |
completed | May 10, 2026, 12:20 a.m. |
| PD | Predicate disambiguation | batch_69ffccde2a8c81908e055e74077dbd19 |
completed | May 10, 2026, 12:10 a.m. |
| PDg | Predicate description generation | batch_69ffcf4631cc8190aefa4b8f0b940b89 |
completed | May 10, 2026, 12:20 a.m. |
Created at: May 3, 2026, 4:32 p.m.