Triple
T34391734
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Estonian Citizens' Committees |
E882721
|
entity |
| Predicate | formedInOppositionTo |
P21876
|
FINISHED |
| Object | Soviet rule in Estonia |
—
|
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: Soviet rule in Estonia | Statement: [Estonian Citizens' Committees, formedInOppositionTo, Soviet rule in Estonia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formedInOppositionTo Context triple: [Estonian Citizens' Committees, formedInOppositionTo, Soviet rule in Estonia]
-
A.
emergedInOppositionTo
chosen
Indicates that one entity came into existence or gained prominence specifically as a reaction or counter-movement against another entity.
-
B.
opposedBy
Indicates that one entity actively resists, disagrees with, or works against the actions, views, or position of another entity.
-
C.
designedToOppose
Indicates that one entity is intentionally created or configured to counteract, resist, or work against another entity or process.
-
D.
opposedBecause
Indicates that one entity is opposed to another specifically due to a particular reason, cause, or justification.
-
E.
opposedDuring
Indicates that one entity actively resisted or was in conflict with another entity during a specified time period or event.
- 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_69f349c1304081909331872829e38106 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a0008225cc081909ff1fd0639859dc4 |
completed | May 10, 2026, 4:22 a.m. |
| PD | Predicate disambiguation | batch_6a0007bac5d8819098aff8031d4abe5d |
completed | May 10, 2026, 4:21 a.m. |
Created at: May 1, 2026, 1:59 a.m.