Triple
T26870381
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PARNAS party |
E676594
|
entity |
| Predicate | stanceOnMedia |
P162826
|
FINISHED |
| Object | opposition to state media monopoly |
—
|
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: opposition to state media monopoly | Statement: [PARNAS party, stanceOnMedia, opposition to state media monopoly]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stanceOnMedia Context triple: [PARNAS party, stanceOnMedia, opposition to state media monopoly]
-
A.
stanceOnMedia
chosen
Indicates a subject’s expressed attitude, opinion, or position toward a particular media outlet, medium, or piece of media.
-
B.
stanceOn39Articles
Indicates a subject’s position, view, or attitude toward the Thirty-Nine Articles (typically of the Church of England).
-
C.
stanceOnAuthority
Indicates an entity’s attitude, position, or level of support or opposition toward authority or authoritative control.
-
D.
publicStatements
Indicates that one entity makes official or public verbal or written declarations about another entity or topic.
-
E.
stanceOnProofs
Indicates the position or attitude an entity holds regarding the use, value, or nature of proofs.
- 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_69eee9ba94bc8190b44c5d4397d04ecd |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f6352fdb788190b9bad30243690743 |
completed | May 2, 2026, 5:32 p.m. |
| PD | Predicate disambiguation | batch_69f631850ae08190a0ba51e4f1e4ccb3 |
completed | May 2, 2026, 5:16 p.m. |
Created at: April 27, 2026, 5:32 a.m.