Triple
T15290079
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Livonian people |
E365502
|
entity |
| Predicate | affectedByPolicy |
P25489
|
FINISHED |
| Object | Russification |
—
|
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: Russification | Statement: [Livonian people, affectedByPolicy, Russification]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: affectedByPolicy Context triple: [Livonian people, affectedByPolicy, Russification]
-
A.
targetedByPolicy
Indicates that an entity is the intended subject or focus of a specific policy’s rules, actions, or effects.
-
B.
areAffectedBy
chosen
Indicates that one entity experiences an effect, influence, or impact as a result of another entity or event.
-
C.
endedPolicy
Indicates that a previously active policy has been brought to an end or terminated.
-
D.
appliesToPolicy
Indicates that something is relevant or applicable to a particular policy.
-
E.
establishedPolicy
Indicates that a policy has been formally created, adopted, and put into effect as a guiding rule or standard.
- 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_69d85a103d9081908c1ea6c4c73ac8e3 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e00e5635b4819092a69b5806d15bff |
completed | April 15, 2026, 10:16 p.m. |
| PD | Predicate disambiguation | batch_69deca90739081909bd1b797cdb8af2b |
completed | April 14, 2026, 11:15 p.m. |
Created at: April 10, 2026, 3:15 a.m.