Triple
T18576388
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Memorial |
E453997
|
entity |
| Predicate | continuesActivitiesAs |
P132649
|
FINISHED |
| Object | international network outside Russia |
—
|
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: international network outside Russia | Statement: [Memorial, continuesActivitiesAs, international network outside Russia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: continuesActivitiesAs Context triple: [Memorial, continuesActivitiesAs, international network outside Russia]
-
A.
continuesWorkBy
Indicates that one entity carries on, extends, or further develops the work previously initiated or performed by another entity.
-
B.
continuesFor
Indicates that an event, state, or process persists or remains in effect for a specified duration or period.
-
C.
performActivities
Indicates that an entity carries out or engages in one or more specified activities or tasks.
-
D.
laterActivity
Indicates that one activity occurs after another in time, establishing a temporal ordering between them.
-
E.
continuedThrough
Indicates that an event, state, or process persisted without interruption across or beyond a specified point, period, or boundary.
- 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_69d8d38974308190a9174430ef256b73 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e543c9d26c8190a80dda411cd0c9ac |
completed | April 19, 2026, 9:06 p.m. |
| PD | Predicate disambiguation | batch_69e478c98d4c81909d37a0e72c6e7bd0 |
completed | April 19, 2026, 6:40 a.m. |
| PDg | Predicate description generation | batch_69e484121cd48190bf583b4c94636a30 |
completed | April 19, 2026, 7:28 a.m. |
Created at: April 10, 2026, 11:43 a.m.