Triple
T23851731
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Соборная площадь |
E592186
|
entity |
| Predicate | социальнаяРоль |
P268
|
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.
socialRoleIn
Indicates that one entity holds a particular social role, status, or position within the context or framework defined by another entity.
-
B.
socioeconomicRole
Indicates the social and economic position, function, or status an entity holds within a society or system.
-
C.
role
chosen
Indicates the function, position, or responsibility that one entity holds in relation to another within a given context.
-
D.
ethnicRole
Indicates a role, function, or social position that is specifically associated with or defined by an entity’s ethnicity.
-
E.
profileRole
Indicates the specific role or function an entity holds within a given profile or contextual configuration.
- 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.