Triple
T34649480
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Челкаш |
E889793
|
entity |
| Predicate | тематикаСвязь |
P49998
|
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.
повʼязанеЗ
Indicates a general association or connection between one entity and another.
-
B.
majorThemeAssociation
chosen
Indicates that one entity is associated with another as a primary or central theme.
-
C.
thematicConcept
Indicates that one entity embodies, expresses, or is centrally concerned with a particular underlying theme or conceptual idea represented by the other entity.
-
D.
topicOfDiscourse
Indicates that something serves as the subject or focus of a particular discussion, conversation, or communicative act.
-
E.
centralThemeConnection
Indicates a relationship where one element serves as the primary or unifying theme that conceptually links or organizes the other element(s).
- 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_69f349d825c88190bfc6170ac9281260 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f722c1bc648190a79bfdc722dcaaa4 |
completed | May 3, 2026, 10:26 a.m. |
| PD | Predicate disambiguation | batch_69f72157af108190880317a62e634bb0 |
completed | May 3, 2026, 10:20 a.m. |
Created at: May 1, 2026, 2:04 a.m.