Triple
T23851744
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Соборная площадь |
E592186
|
entity |
| Predicate | планировочнаяОсобенность |
P32324
|
FINISHED |
| Object | ориентирована на фасад собора |
—
|
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: ориентирована на фасад собора | Statement: [Соборная площадь, планировочнаяОсобенность, ориентирована на фасад собора]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: планировочнаяОсобенность Context triple: [Соборная площадь, планировочнаяОсобенность, ориентирована на фасад собора]
-
A.
hasPlanningCharacteristic
chosen
Indicates that an entity possesses a specific feature, quality, or attribute related to planning activities or processes.
-
B.
planning
Indicates that an entity is engaged in organizing or devising a future action, event, or course of behavior involving another entity or entities.
-
C.
planned
Indicates that an entity has intentionally arranged or scheduled another entity or event to occur in the future.
-
D.
notablePlan
Indicates that an entity is recognized for having a significant or noteworthy plan associated with it.
-
E.
plan
Indicates that an entity intends or arranges for a future action or sequence of actions to occur.
- 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_69e25d221d908190b9b502ad31e66a3f |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1c987c3208190bf3f210d12106927 |
completed | April 29, 2026, 9:04 a.m. |
| PD | Predicate disambiguation | batch_69f1614612b481908c45d99e588882f9 |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 8:11 p.m.