Triple
T32918560
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pavel Korchagin |
E842082
|
entity |
| Predicate | activityDespiteDisability |
P182783
|
FINISHED |
| Object | continues revolutionary work |
—
|
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: continues revolutionary work | Statement: [Pavel Korchagin, activityDespiteDisability, continues revolutionary work]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: activityDespiteDisability Context triple: [Pavel Korchagin, activityDespiteDisability, continues revolutionary work]
-
A.
activity
Indicates that an entity is engaged in or performing a particular action, behavior, or process.
-
B.
activityType
Indicates the specific kind or category of action or event that an entity is engaged in or associated with.
-
C.
activityChallenged
Indicates that one entity has questioned, disputed, or formally contested the validity, appropriateness, or outcome of an activity involving another entity.
-
D.
activityTime
Indicates the time period during which an activity occurs or is scheduled to take place.
-
E.
disabilitySport
Indicates that an activity or competition is a sport specifically designed for or practiced by people with disabilities.
- 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_69f3494779388190a5d3e97f92278be2 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f7908ec35881909a42f954fb9fa16e |
completed | May 3, 2026, 6:14 p.m. |
| PD | Predicate disambiguation | batch_69f78e2ac3fc819081a45c6841375c8d |
completed | May 3, 2026, 6:04 p.m. |
| PDg | Predicate description generation | batch_69f78fd3fd888190b7db0b563f298585 |
completed | May 3, 2026, 6:11 p.m. |
Created at: May 1, 2026, 1:19 a.m.