Triple
T29357608
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stepan Bandera |
E744487
|
entity |
| Predicate | hasPartisanReputation |
P5316
|
FINISHED |
| Object | controversial |
—
|
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: controversial | Statement: [Stepan Bandera, hasPartisanReputation, controversial]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPartisanReputation Context triple: [Stepan Bandera, hasPartisanReputation, controversial]
-
A.
hasOpposedParty
Indicates that one party is in an opposing or adversarial position relative to another party, typically within a dispute, conflict, or legal proceeding.
-
B.
hasPoliticalCharacteristic
chosen
Indicates that an entity possesses a specific political attribute, quality, or affiliation.
-
C.
hasPoliticalComponent
Indicates that something includes, involves, or is influenced by political factors, interests, or considerations.
-
D.
estimatedPartisanStrength
Indicates an assessment or prediction of the degree of partisan support or political leaning associated with an entity or context.
-
E.
nationalReputation
Indicates the recognized standing or esteem an entity holds at the level of an entire nation.
- 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_69f0a79aee588190b490f19d93c6e52d |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69fd67191cf88190b53ecbf5be3564e9 |
completed | May 8, 2026, 4:31 a.m. |
| PD | Predicate disambiguation | batch_69fd654fdaac81908e67e75194710f06 |
completed | May 8, 2026, 4:23 a.m. |
Created at: April 28, 2026, 2:14 p.m.