Triple
T24339471
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Надежда |
E613472
|
entity |
| Predicate | популярность |
P1755
|
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.
popularity
chosen
Indicates how widely liked, admired, or favored something or someone is by a group of people.
-
B.
popular
Indicates that an entity is widely liked, admired, or favored by many people compared to alternatives.
-
C.
peakPopularity
Indicates the time or context in which something reaches its highest level of popularity relative to other times or contexts.
-
D.
isPopularWith
Indicates that one entity is well-liked, favored, or widely accepted by another entity or group.
-
E.
isPopularAs
Indicates that an entity is widely liked, well-known, or favored in a particular role, context, or capacity.
- 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_69e2d7dcc5a08190b53691130d56cbc4 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f2932324e8819082344cf42eddc274 |
completed | April 29, 2026, 11:24 p.m. |
| PD | Predicate disambiguation | batch_69f287ad30048190b3ad3613486f277f |
completed | April 29, 2026, 10:35 p.m. |
Created at: April 18, 2026, 1:57 a.m.