Triple
T35871539
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OSCE Special Monitoring Mission to Ukraine |
E1037238
|
entity |
| Predicate | impartiality |
P76229
|
FINISHED |
| Object | impartial |
—
|
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: impartial | Statement: [OSCE Special Monitoring Mission to Ukraine, impartiality, impartial]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: impartiality Context triple: [OSCE Special Monitoring Mission to Ukraine, impartiality, impartial]
-
A.
impartialityRequirement
chosen
Indicates that a situation or rule requires parties to act without bias, favoritism, or prejudice toward any side involved.
-
B.
requiresJudgeImpartiality
Indicates that the situation or action necessitates a judge to remain unbiased and impartial in making decisions or evaluations.
-
C.
nonPartisan
Indicates that an entity is not affiliated with, influenced by, or acting on behalf of any political party or partisan interest.
-
D.
parity
Indicates that two quantities share the same evenness or oddness, or more generally that they have equivalent status or value in a given context.
-
E.
arity
Indicates the number of arguments or participants that a relation or function takes.
- 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_69f76e1e701c8190a4990d4978ce4fe6 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7aa3883d48190b05e3d2da7a017ae |
completed | May 3, 2026, 8:04 p.m. |
| PD | Predicate disambiguation | batch_69f7a8d435288190b30b1991fb003121 |
completed | May 3, 2026, 7:58 p.m. |
Created at: May 3, 2026, 4:06 p.m.